Here is the one-liner you need to install Atlantis 3 using composer
composer create-project atlantis-labs/atlantis3 --prefer-dist [folder]
Just as a small clarification in case you're trying to search for the public folder. There is no need for that - we have redesigned the code a bit so its very easy to be installed on shared hosts or environments where people don't get an easy access to the web server config. Pointing the server to the root of your installation is all you need to run A3.
Hi, I'd like to try out Atlantis since it looks very promising.
I'd like to know if there is an easy way to install Atlantis above the public directory, like in a regular Laravel install.
Hey! How do you login anywhere after install. I thought this should be pretty straight forward.
The first mention mention of login is in this paragraph.
By default, Atlantis does not have any activated WYSIWIG editor for your profile . We leave that option to you, however in the modules repository tab you can find CKEditor a available but you need to install it and activate it first. The next step is to go into your profile settings on the top left side and in the editor dropdown choose CKEditor. You can of course at any point install different editor module and use it instead, just by changing your selection in your profile. At the moment, a module for the Codemirror editor is also available and ready for usage.
Please if there is anything laravel has taught us, is the fact that things have to be simple and intuitive. I finished installing your app and then I had no ideas even from the documentation what to do next.
@selase : I am sorry about that, we will add this to the documentation. After your install the way to access the admin is going to /admin on your host. As the docs state the default login is user: admin , password: admin123 . Once you are logged in your user settings are on the top left and you have to install whatever editor you want from the Modules Repository. Its really easy - there is a list of available modules you get once you click the "repository" button and you get to install them with one click.
@gwleuverink : Hello. Atlantis is designed to be easy to be installed on shared hosts and it does not require any specific webroot setup. Its enough to point your server to the index file in the root folder of the install to make it run. That being said: you don't need public folder anymore. We're probably going to remove it from the distro so it does not mislead people.
@evgeni Thanks a lot for the response. Add that to the documentation and perhaps this will be a good time to add a youtube video. Naturally the next place I went to look when I didn't seem to get what I wanted was youtube. For this product to be adopted quickly that could be crucial as well. And also remember to have examples of how things are done from A to Z. For example I just checked how to build a theme and the information is woefully inadequate. Even for experienced developers it helps if the documentation is presented from 1st principles. Basic do this and that and then this. Thanks for the quick responses.
@evgeni Thanks for your reply. I understand that it isn't a necessity since the application architecture is tweaked. But i'd like to install the framework and all other packages outside of the public directory.
I really do understand the need to make it accessible to people who don't don't have administrative rights on their server. But I prefer not to have it like this for two reasons:
I understand that it might not be as straight forward to provide this feature but if you can provide a way to install and use the package outside of the public directory as an option that would be great.
Don't get me wrong, i'm not trying to second guess any of your decisions. Just want to know if it's possible.
@selase Thanks! We are trying our best but we also have daytime jobs, hopefully we can get some people involved to help us push this forward, but I do appreciate what you're saying.
@gwleuverink : Appreciate your questions. If you inspect the htaccess file that comes with A3 you will see that we block the access to a lot of places public is not suppose to see. As a matter of fact even not all media files are allowed ( you can see the ones that are by default there ). If I am understanding what you are asking is that you want to have a standard "laravel" web server setup with "public" being the web root and still have the CMS working fine. If this is the case - you can try to move the index.php from the root to the public and experiment with adjusting the paths of where things load from. However I will advice for you to check the .htaccess first.
@evgeni Thanks for clarifying. I have to admit I didn't check the .htacces file yet. I'll explore the CMS more next week but I have to say I really enjoy the experience so far.
@gwleuverink You can pull an update with "composer update" there is an additional security rule added. Thanks for your feedback.
How to install with Composer as a package on an existing Laravel project?
Apparently like this:
composer require atlantis-labs/atlantis3-framework
Could you please update the docs
Hm, well, Atlantis comes with Laravel but as the docs state it won't work with its default structure like "public" folder also comes with its own .htaccess, so I don't think you can do that.
@KingRichard are you sure your webserver is obeying and loading the provided .htaccess file?
It looks like you're new here. If you want to get involved, click one of these buttons!