Quick Start
Prerequisites
Before setting up Atslegas, ensure your system meets the following requirements:
- Python: version 3.7 or higher.
- Pip: Python package manager.
- Browser: Modern web browser (Chrome, Firefox, or Edge).
1. Installation
Clone the repository and navigate to the project root directory:
git clone https://github.com/JamesAce60/ARS.git
cd ARS
Install the required Python dependencies using pip:
pip install -r requirements.txt
2. Configuration
The application uses a config.json file located in the root directory for core settings. Before launching, ensure your config.json contains a secure secret key for session management:
{
"secrets": {
"flask_secret_key": "your_secure_random_string_here"
},
"client_sessions": {
"timeout_seconds": 3600,
"session_storage_dir": "%s/flask_session"
},
"db": {
"db_file": "database.db",
"schema_file": "schema.sql"
}
}
Note: The application will automatically create the SQLite database file and initialize the schema on the first run.
3. Launching the Application
Start the Flask server by running the entry-point script:
python main.py
By default, the server will start in debug mode at http://127.0.0.1:5000.
4. Initial Access
Once the server is running, you can access the interface through your browser. The system initializes with a default administrative account:
- URL:
http://localhost:5000 - Username:
root - Password:
root
Administrative Setup
Upon logging in as root, you will have access to the Admin Dashboard. It is highly recommended to immediately:
- Navigate to User Management.
- Update the
rootpassword or create a new administrator account. - Configure Key Groups and Persons to begin managing assets.
Common Troubleshooting
- Database Locks: The system uses SQLite in WAL (Write-Ahead Logging) mode. If you encounter "Database is locked" errors, ensure no other process is holding a manual lock on
database.db. - Session Issues: If you cannot log in, check that the
flask_session/directory is writable by the application. - Missing Config: If the application fails to start, verify that
config.jsonis present in the root folder and follows valid JSON syntax.