Years ago, I built several Drupal/Joomla/Mambo/Wordpress websites on OpenSuse Linux. At the time, I used Yast(2) to create the website and configure various settings. I understand that Yast(2) is no longer supported and that its functionality will gradually disappear. At the time, I also worked with webmin and have read here and there that it is a good option for configuring things. I don’t mind editing config files manually, but it’s quite a quest to find the right ones and set them up.
Now I want to take it up again as a hobby, this time with Ubuntu Server and Typo3.
I don’t know where to start. I used to put my virtual hosts in the “/srv/www/html” folder, but that no longer exists. Now there is a “/var/ww/html” folder, and there is a public folder in my home directory.
When I start typo3 with “composer exec typo3 setup,” a “public” folder is also created in my project folder.
Where do you recommend I create my project?
Where should I point my virtual host?
In OpenSUSE, the user was “wwwrun” and the group was “www,” I believe.
Now I see “www-data” as the user and group.
Do you recommend setting it up with Apache2 or Caddy? I understand that Caddy would work automatically with Let’s Encrypt.
What folders are available in a TYPO3 installation depends on the way you choose to install it. TYPO3 has two different modes that will give you somewhat different folder structures:
Composer-based setups are ideal for advanced projects or team-based workflows. They are common in professional environments with development teams. This is the mode used when installing TYPO3 with DDEV.
Classic mode is ideal for managed hosting, automated updates by the hosting provider, and simpler setups. It is also well suited for beginners due to the GUI-based extension handling. It includes access to the TYPO3 Extension Repository (TER) via a regular backend module.
The typical directory structure of a TYPO3 installation differs fundamentally between Composer mode and Classic mode. It can also vary depending on the TYPO3 version. Since TYPO3 v12 only classic mode makes use of the typo3conf folder. Composer-based installations rely on Composer’s vendor folder and a configuration folder called config. More information about the directory structure.
You’ll also find that Composer mode is introducing a public folder. It is good practice to keep as much as possible of the executable code away from this folder. The Composer-based installation does this for you, for example, symlinking the necessary public assets from extensions into public/_assets. Classic mode does not do this.
There is much to be said about exact setups on different servers, but whatever you usually call your folders on the server environment of your choice, a Composer-based installation will try to work with a public folder. Making /srv/www/html your webserver’s public folder is still possible, just make /srv/www your Composer root and make html a symlink to the public folder.
I hope this was helpful. Please feel free to ask further questions.