It seems I set up everything correctly. I received no errors.
I used zf create project and it created the project no problem.
I went to localhost/site and instead of showing the welcome to zend page it opens the directory and shows me its contents. I have to go to localhost/site/public to see that page.
I tried creating a new public action in the controller and added a file in the view scripts portion but it didn't show up.
The project is located in /var/www/html directory
What could I have forgotten?
Steps I took:
Updated repositories before downloading and installing stuff
Install linux
install apahce
install mysql
install php
install phpmyadmin
install zend framework minimal
install phpunit
install subversion (but did not combine it with zend)
That's about it, I didn't do anything more than that.
By default it is assumed you will run the project from a Virtual Host with the DOCUMENT_ROOT pointed at /path/to/project/public If you want to run the site in a subdirectory then this subdirectory should only contain the contents of what is currently in public, and you would need to modify the configuration settings to run with this setup.
Check out the Quickstart section "Create a Virtual Host" for more info.
The easier option here is just to create a Virtual Host for the project and add a host entry to /etc/hosts like:
127.0.0.1 zfproject.local
Related
Has anyone here been able to install Snipe-IT (Open source asset management: https://snipe-it.readme.io/docs) on Azure Web Apps?
I know it is possible to install it on an Azure VM, since I've done that, but I would prefer it to be on a Web App so we keep everything simple and slightly more secure.
I have been able to download it from GitHub, and it then says that the document root is incorrect (It has to be \wwwroot\public instead of \wwwroot). So, I go ahead and change the document root to the public, but then the page returns a 500 error. I see that I need to install Composer, so I install the extension for that, but nothing changes. I know the document root works correctly because I am able to place a test file in the public directory and it works fine. It is just the actual Snipe-IT install that gets screwed up.
Here's how I did it:
Run the command composer install under \wwwroot folder to install dependencies.
Change the document root by setting the virtual application path for the web app.
Edit the Snipe-IT configuration file (.env file) to configure the database credentials, app key and so on.
Restart the app service.
Finally, It worked for me.
I'm still really new to Git version control and Laravel. But I have gotten so far, and I'm not sure now where I am going wrong.
I set up VirtualBox and Vagrant on my local windows machine and installed homestead successfully. I have managed to get my Laravel website (it's only one page at the moment as I learn things) working correctly, it displays the header and the footer and the images load and everything. So that's all good.
So now, I have my Laravel website set up within my virtual vagrant server. On this server, the directory for my website is:
/home/vagrant/Code/sites/public_html
No when I cd to that directory, I ran the following:
git init
get remote add origin https://user#repo/user/publichtml.git
git add *
git commit -m "Initial Commit"
git push -u origin master
(I've substituted user#repo instead of the real URL)
All went through successfully. Great. So now on my live server I ran the following:
cd /home/sites/public_html
git init
git clone https://user#repo/user/publichtml.git
Which again, worked fine. It downloaded all the files into the public_html directory which is great. So then I go to visit the website and this is what I get:
The only explanation for this happening is maybe I need to install something on the server before I clone these files to it. I guess the files in the Laravel folder won't run by themselves? Do I need to install composer and laravel on the server or something? If so, how do I do that, and why don't they run on their own?
I cannot see a .htaccess or index.php in the root directory so I am not sure how it runs anyway.
You should install Laravel using composer instead.
composer create-project laravel/laravel mysite
You should also point the document root on your web server to laravels "/public" folder, making the framework code reside outside of the document root. That's good for security (no one can access any framework code, like your configs etc directly).
You will then find the .htaccess-file in the /public folder.
Please read the Laravel documentation about the different but recommended ways to install Laravel.
Btw, doesn't homestead use Nginx instead of Apache? In that case, .htaccess isn't even used. Please refer to the Laravel documentation again regarding homestead.
You need to redirect traffic to public/index.php instructions for this are webserver dependent.
I am new to Magento. I have installed Magento on localhost and I am using XAMPP (Windows) server. The installation was successful.
And when I opened the home page, it was so blank with no images on it
Store home page:
When I opened the console I got the following errors
Console errors:
How do I fix this?
It is a common problem on windows servers (mostly local xampp servers) because these servers dont have symlinks.
Do this to fix it:
go to app/etc/di.xml and delete name="view_preprocessed" in virtualType name="developerMaterialization" section.
go to pub/static and delete all files except the .htaccess
after that I installed it again and it worked
Install composer. You can use Composer to install Magento 2. It is a tool for dependent management in PHP which allows you to declare the dependent libraries your project needs and install them for you. Composer enables you to manage Magento 2, extensions, and their dependencies
Check permissions of the /pub/media and pub/static folders
system permissions for Magento 2
I'm in a trouble trying to install phpBB on openshift.
I have created a php5.3 cartridge with PostgreSQL: I unpack phpbb on a folder of my app, I push the change, then I run the installation form the browser.
The forum installation is successful.
In the end I need to delete the "install" folder in order to enable the forum.
I tried it on my standalone wampp server and it works.
So I delete it in my repo, and I commit and push the change.
When the app restarts it automatically tries to go back to the installation: everything is broken.
It seems the push breaks the configuration on the server side.
I also have tried to change the name of the directory using ssh connection, and move the install directory name: this is uneffective.
What's the problem here?
The problem is that if you deploy the phpBB package as downloaded from official website app the files will go on app-deployments with are not persistent on git changes and can not be pull to local. You can try using the OpenShift quickdeply version of phpBB (https://github.com/openshift-quickstart/phpbb-example) that deploys the files to app-root/data (I think :S) and this reamins untouched on git changes.
The "install" folder is at app-root/runtime/repo/php
While installing laravel through terminal command, my other projects in MAMP htdocs folder got affected and they are not working.
I followed this process for installing laravel
Those directions have you symlink the "htdocs" directory to your laravel install, effectively making your htdocs directly useful only for Laravel.
You should avoid this, perhaps by creating a symlink from your laravel build to a directory within htdocs. For example, linking to a directory in htdocs called "mylaravelapp": ln -s /path/to/laravel-master /path/to/htdocs/mylaravelapp.
Lastly, consider using Vagrant or another virtual machine provider instead of MAMP for a server. You'll have to get through a learning curve (potentially), but you'll end up better for it. This creates a virtual server for you, which won't interact with any other parts of your Mac (YOu can make a server per project!).
Here is a guide to get started with Laravel 4 and Vagrant.