I installed a completely new Neos package (clean install from scratch).
Then I tried to begin with the german tutorials found on punkt.de.
Beginning with tutorial 2, after issuing these commands and creating and importing a new site, I only get 500 server errors. 500 errors are on the frontend as well as on the backend - login still works, after the login the 500 occurs.
Instead of your apache error log, can you look in the Neos Flow System log located in Data/Logs/System_Development.log - it will give you more detailed information about what happened.
Hi, I’ve had a look at the System_Development.log, but couldn’t find anything really interesting there. There is so much information that I’m loosing the overview.
Question: Is the above outlined method of deleting/pruning the sites and creating a new site nowadays still the preferred method/best practice doing that?
Or did things change in ongoing development of Neos? I’m using version 3.1.
Where is the difference in creating a new site package on the console with the neos user and creating it within the backend module?
As I found out, the backend module does not delete/prune all previous stuff. Better?
I really have my difficulties getting startet with Neos.
Hi David, thanks for replying. I decided to do a new clean install.
At that moment I noticed that when running in production mode the install tool doesn’t work.
I don’t know if that’s okay, but commenting prod mode out in apache site config did the job. So now I am on a clean install with a clean database.
But anyway - the above code for deleting/pruning sites and kickstarting a new one - is it okay? Or do you understand why it leaves me alone with 500’s ?
Are there any commands missing? Or is it better to create a new site package within the backend?
Or did things change in ongoing development of Neos? I’m using version 3.1.
The tutorial is up to date with the current version of Neos.
But anyway - the above code for deleting/pruning sites and kickstarting a new one - is it okay?
Yes it is. It is important to remove the demo package, as its configuration influences every own site package you create. Using the commands is absolutely fine and ensures you remove the package and code completely.
I’m running Neos in production context.
You shouldn’t do that. With production context a lot of caches kick in and you cannot change anything without flushing the caches. That is why the setup - which tries to change configuration - is also not working.
I really have my difficulties getting startet with Neos.
I would recommend to really stick to the tutorial. We use it to get complete beginners, even without much knowledge about web development into working Neos. The tutorial is actively used and therefore testet and I get a lot of positive feedback So try to use the provided vagrant environment which saves you from a lot of configuration hassle and try to stick to the steps and you will get a running neos without the mentioned problems.
Great, so I now know that it’s up to date and you’re having an eye on it.
Okay, okay. I will switch back to dev mode.
Is it okay to you if I want to stay on my freshly setup Ubuntu 16.04.2 VM with standard apache installed? I set this VM up on one of my ESXi hosts, so that this VM sits in the DMZ. I configured apache to allow connections for the dev subdomain/virtual webserver only for my local network. I think this way I’m much more close to the final host (VM) so that I don’t get in trouble when finally moving the site off the vagrant VM to the destination host.
