cube/myriad
2
1
Fork 0
Code Issues 29 Pull Requests Projects 2 Wiki Activity

Merge branch 'master' of https://tea.cubes.link/cube/myriad

Browse Source
This commit is contained in:
cube
2026-05-28 01:49:47 +01:00
parent 2fcce4cbbe 1f3081471b
commit 71cc1d0357
1 changed files with 2 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
README.md
View File

@@ -32,7 +32,6 @@ TMP_FOLDER = 'myriad/static/tmp' # required for exports
SYSTEM_NAME = 'Myriad' # will be shown in the title bar SYSTEM_NAME = 'Myriad' # will be shown in the title bar
PAGES_NAME = 'Read More...' # will be shown in the nav bar if using custom pages PAGES_NAME = 'Read More...' # will be shown in the nav bar if using custom pages
SECRET_KEY = "dev" # CHANGE THIS - see wiki for details SECRET_KEY = "dev" # CHANGE THIS - see wiki for details
``` ```
most likely if you get an error after updating, you need to make sure your config has all the fields as sampled above. we may have added something that you now need. most likely if you get an error after updating, you need to make sure your config has all the fields as sampled above. we may have added something that you now need.
@@ -61,11 +60,9 @@ flask --app myriad register-admin --username EXAMPLE_USER --password EXAMPLE_PAS
there are currently various ways to export and import data for use within myriad. individual member exports and imports deal only with the fields (though icons, stamps, and blinkies can be exported to a zip folder). they're designed to be used with an active database for whatever purpose the user requires. there are currently various ways to export and import data for use within myriad. individual member exports and imports deal only with the fields (though icons, stamps, and blinkies can be exported to a zip folder). they're designed to be used with an active database for whatever purpose the user requires.
the other option is to export the entire system to json or zip file. **importing an entire system is best used on a completely empty database, as it deals with inserting id fields**. a full system import is useful for when an update is released that requires the database to be re-initialised, you can quickly restore information and images you had before. the other option is to export the entire system to json or zip file. **importing an entire system is best used on a completely empty database, as it deals with inserting id fields**. if the database is not completely empty, there may be some weird importing errors. a full system import is useful for when an update is released that requires the database to be re-initialised, you can quickly restore information and images you had before.
both are a little janky as they've just been implemented rather quickly to cover the base requirement of being able to migrate the database in some form. **don't rely on them, be sure to keep your own backups**. **please don't rely entirely on our software, be sure to keep backups of your own data**.
**individual member import via zip folder is not currently possible**
# Development set up (Windows) # Development set up (Windows)
@@ -79,7 +76,3 @@ both are a little janky as they've just been implemented rather quickly to cover
- The software here is free to use, and there's no requirement to link back - The software here is free to use, and there's no requirement to link back
- Edit the styles and functionality to suit your needs. I'm sure some of you out there are far better with CSS than us - Edit the styles and functionality to suit your needs. I'm sure some of you out there are far better with CSS than us
# Preview
[Check out our own personal instance](https://system.cubes.link)