I installed Silverstripe via Composer, just as described in the Silverstripe lessons.
It worked fine and the page is accessible by localhost.
I'm using XAMPP (newest version) with Apache and MySQL running.
Plugin php-intl is also enabled.
However, when I try to access the site it shows me the following message:
SilverStripe Framework requires database configuration defined via .env
I should see an install page, but there's just this message.
It is a completely fresh Silverstripe project. No changes have been made.
What can I do to fix this problem?
As described in the Silverstripe getting started guide we need to create a .env file and set it up with our environment variables.
W create a .env in our project root (not the public/ folder). In this file we set up the minimum required environment variables. Replace the placeholders as required:
SS_DATABASE_CLASS="MySQLDatabase"
SS_DATABASE_NAME="<database>"
SS_DATABASE_SERVER="localhost"
SS_DATABASE_USERNAME="<user>"
SS_DATABASE_PASSWORD="<password>"
SS_DEFAULT_ADMIN_USERNAME="admin"
SS_DEFAULT_ADMIN_PASSWORD="password"
SS_ENVIRONMENT_TYPE="dev"
Now we should be able to build our database by visiting http://<local-website-url>/dev/build.
Our website should be available on our local domain now.
Note, Silverstripe previously was packaged with an installer UI. This was removed from the core framework in version 4.5 and moved into it's own separate silverstripe-installer-wizard module. This can be added to the project by running composer require silverstripe/installer-wizard.
Related
I'm working on an old Symfony 2.5 application. I don't have SSH access on the server, I can't do the cache:clear command or any other Symfony command. I don't have access to the git repository either. I'm working with a manual backup made from the production server.
I made some changes to the Twig template, the changes are shown in DEV but in Production, the changes do not appears.
If I manually delete the /cache/prod/twig folder from the server, will it clear the cache and can it break the site.
There is also a 'deploy' file, which is a shell script, but I don't know which deployment platform has been used in the past with this file. Does someone know about this file.
Thanks
I am trying to create a web server with XAMPP to host an ASP.NET website. However, I am unable to do so. As I understand it, ASP.NET apps cannot be served out-of-the-box with XAMPP. I have found that in order to get Apache to work through XAMPP that mod_aspdotnet needs to be installed and configured. I am following the instructions for mod_aspdotnet by Shehroz Kaleem at https://xehroz.tumblr.com/post/43884721903/how-to-run-aspnet-on-xampp, but I am running into issues. First off, the current version of mod_aspdotnet (https://sourceforge.net/projects/mod-aspdotnet/files/latest/download) is in a zip file that does not include an installer inside of it (or at least, I can't find one). This makes installing it a problem. So, in order to fix that issue, I have resorted to attempting to use the previous version (2.2.0.2006) that is not a zip file, but a directly installable .msi. The problem with this installer, however, is that it does not recognize C:\xampp\apache as a "valid path to an installed instance of Apache." This install location from XAMPP is suggested in the aforementioned instructions by Shehroz Kaleem. Does anyone have any experience setting up a web server for ASP.NET using XAMPP? Is there something that I am doing wrong?
I'm migrating an ASP.NET 5 Web App from manually deploying in Visual Studio to deploying through an ARM template. I can successfully provision the website and the deploy claims to succeed, but whenever I hit my endpoint I get a 404. It doesn't seem to be a configuration issue, as if I deploy the same web app into the same container through VS it works as expected.
Browsing through the files on the site, the only difference I can see is that there's no web.config when published through ARM, and I'm wondering if that might cause it.
The way the deploy seems to work is that ARM is calling "dnu pack" on my xproj to create a nupkg, and that deliberately strips out the web.config file. I get the following message:
The following commands will not be exported for global install: web.
I can't see any way of forcing "dnu pack" to include web.config.
Most of the documentation I can find refers to using a .zip file to upload, but that seems to be only for older versions of ASP.NET. Anyone got any pointers?
What is the proper way to deploy webapps on Heroku? I'm installing Moodle, but the same procedure should apply to e.g. Drupal or Wordpress. What I hace done is to unzip Moodle locally, then uploaded it using git to Heroku. When I then visit my site I get the option to install it and select the database, which works fine. The problem is that the install procedure saves information in the filesystem on the server, which gets overwritten next time I deploy my app. So what is the proper way of doing this?
You have to pre-configure your app with all of the database settings before you deploy to Heroku. So either do a fake "install" on your local environment, or manually edit your php config files.
As you've discovered, Heroku's filesystem is not persistent: https://devcenter.heroku.com/articles/dynos#ephemeral-filesystem.
there seems to be a small issue I am experiencing. I am trying to migrate a drupal website existing on a production environment onto my development environment.
I did an sql dump of the databases on the prod environment, and installed the same version of Drupal on my local, changed the base url, and took note of the database it was connected to. However, while running the install.php, I mention the exact same db and the credentials.
Drupal is unable to recognize this database. Also, isn't setting up a new Drupal installation going to overwrite the existing database which is the scenario given that I am downloading an existing website and setting it up locally.
Anyone have any leads on this?
Thanks!
First, install Drupal in the development environment, which will let it correctly configure the values in the config file. Then drop all tables in the development database while keeping the database itself intact, including its permissions. Import the database contents of the production environment into the development database.