-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[RFC] Maintenance Mode - suggestion #49
Comments
Ubiquity is not a CMS, but it's a good idea... |
Yes (not a CMS, is a framework), and yes disable Url except admin routes. |
The maintenance mode can be tested before its integration in version 2.1.5 ( For the principle (in the background), the maintenance mode works by adding a route to a maintenance controller, excluding for example administration (Urls starting with I will add by default a comingSoon mode (for the example). Maintenance is accessible in the webtools in the Maintenance section. I have not yet integrated the REST Urls, and the maintenance mode is not accessible with the devtools. |
I got a fatal error Do i forgot to do something? I ran it on a almost blank project (it has only a model) |
you must explicitly include webtools: see #50 |
`· The project folder is C:\wamp64\www\ubiquity\html
|
maybe the devtools are not up to date... |
2.1.5
|
I will update everything to dev-master (ubiquity, devtools, webtools) see what happens |
Update
After update
Fetching version
|
only the update of the devtools is global |
Step 1: downgraded global ubiquity and webtools - OK
Step 2: Create a new project Step 3: tried to check
Step 4: Inside project folder, switch all to dev-master: OK
Step 5: Tried to get ubiquity version again and got same fatal error before - ERROR
|
Edit manually your global Then restart the procedure:
|
Step 1: Remove unused packages - OK Edit manually your global composer.json to remove all unused packages: in C:\Users\Gildonei\AppData\Roaming\Composer Then: composer global update It seems you have an old version of Ubiquity classes in the global composer file Result composer.json file
Step 2: - Check version - OK
Step 3: Create new project - OK
Step 4: Check version again (outside project folder) - OK
Step 5: Run in browser http://ubiquity.local - OK Step 6: Check version again (inside project folder) - ERROR
Stoped here - Should I continue and update to dev-master? |
Yes, for the moment it's normal, |
Continuing Step 6: Update ubiquity to dev-master (inside project folder) - OK Step 7: Run in browser http://ubiquity.local - ERROR
Step 8: Update webtools to dev-master (inside project folder) - OK Step 9: Run in browser http://ubiquity.local - ERROR
End of steps |
Can you try again in the same project: |
Now It works perfectly. Inclusive maintenance section. |
@gildonei No negative (or positive) feedback on the maintenance part? |
Hi @jcheron. I didn't had time enought to test this feature until now.
A great job as always. Thank you again for all your work. I think we can close this topic. |
Thank you for this feedback @gildonei A small correction about deactivation: it is not automatic. |
Deactivation: understood. Anyway it is a good resource for visitors to have an estimated time. |
Summary
I think would be nice if Ubiquity have a native maintenance mode, that could be activated in config through webadmin or devtools, and when in maitenance, it only allows backend access interface, and in front a page with a maintenance message or similar
Motivation
All major CMS (WordPress, Joomla, Drupal) have a similar functionality, that allows properly config system without break the front, keeping a maintenance page and maybe an http respose
Compatibility with Ubiquity's philosophy
Indicate compatibility or improvements in:
Expected results
Visitors of website developed with Ubiquity will see a maintenance page instead of the site while It is setted to be down.
The text was updated successfully, but these errors were encountered: