Verified Commit 8c0b7ba0 authored by Gael Yvert's avatar Gael Yvert
Browse files

more admin doc; and actually update .env.example this time

parent ff7a4f83
......@@ -165,10 +165,14 @@ You can organize your users and roles in two ways:
## Front-End vs. Back-End <a name="Front-endvsback-end"></a>
An important thing to understand when administering the application is the distinction between the Front-End and the Back-End of it.
An important thing to understand when administering the application is the distinction between its Front-End and its Back-End.
Nearly all web-applications offer two interfaces: the front-end is for users, and the back-end is for the administrator. MyLabStocks also offers two interfaces but the distinction is slightly more subtle:
- The ***Front-End*** is where users can rapidly browse some, **but not all**, of the stocks. The Front-End offers convenient filters to search for specific items and information. Views are organized to be synthetic and rather compact. In other words, the Front-End is for everyday usage, for everyone. The address of the Front-End interface is typically `url-of-your-server/mylabstocks/`.
- The ***Back-End*** is both for the administrator(s) and the users. The administrator can perform all admin tasks such as modifying any table, add users, assign permissions etc. The users can also visit the Back-End to have access to advanced features of MyLabStocks: in the Back-End, they can browse the entire database, provided that they have the necessary permissions. They can add and edit records, which is not possible from the Front-End. The address of the backend is typically `url-of-your-server/mylabstocks/admin/`.
So, keep in mind that it is normal usage of the application to navigate back and forth between the Front-End and the Back-End.
*[Back to Contents](#Contents)*
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment