Commit f3867cc7 authored by Spctrl's avatar Spctrl

Increase version number to 0.9.0~ynh2 to see if I get it as an upgrade in the admin panel

Added how to upgrade and check the Pleroma version in the README file
General touch-ups in comments and README
parent 0a94c6f6
......@@ -27,7 +27,7 @@ What should work:
* Installation
* Removal
* Backup
* Restore
* Restore (You'll need to remove the instance prior to restore. This should change in the future.)
What does not work:
* upgrade
......@@ -36,11 +36,13 @@ What does not work:
What is not implemented:
* There is no LDAP integration. Users on Pleroma are seperate from the yunohost users
* There is no integration with a mailbox and/or -service. This means that mails won't be sent from the application
* I'll probably want to add the Pleroma source in the package eventually. Right now I get it from the Pleroma repo directly during install
* I'll may want to add the Pleroma source in the package eventually. Right now I get it from the Pleroma repo directly during install
Extra info:
* On installation you'll be able to chose a dedicated domain for Pleroma. You'll also be asked for a username and password a user. This user will have moderator rights.
* Pleroma will be listed in the admin-panel under services, so you can stop and start the service there.
* On installation you'll be able to chose a dedicated domain for Pleroma. You'll also be asked for a username and password for a user. This user will have moderator rights. Note that the password will be visible if you install using the `--debug` flag!
* Pleroma will be listed in the admin-panel under services, so you can stop and start the service there
* Postgresql will also be listed in the admin-panel
* You can choose to close sign-up on installation, but you'll need to create invite tokens if you want others to join your instance as well. You can do this by accessing your yunohost server over ssh and run `cd /var/www/pleroma/pleroma/ && MIX_ENV=prod mix generate_invite_token`. See: https://git.pleroma.social/pleroma/pleroma/wikis/Admin%20tasks
* You can choose to close regstrations on installation, but then you'll need to create invite tokens if you want others to join your instance as well. You can do this by accessing your yunohost server over ssh and run `cd /var/www/pleroma/pleroma/ && MIX_ENV=prod mix generate_invite_token`. See: https://git.pleroma.social/pleroma/pleroma/wikis/Admin%20tasks
* If you're not afraid of the terminal, check out https://git.pleroma.social/pleroma/pleroma/wikis/home to see what more you can do with your awesome instance!
* You can upgrade your Pleroma instance by logging in over ssh as root and run `su - pleroma -c "cd /var/www/pleroma/pleroma;git pull;MIX_ENV=prod mix deps.get;MIX_ENV=prod mix ecto.migrate;" && systemctl restart pleroma`
* To check your current Pleroma version you can go to `yourdomain.tld/api/v1/instance`
......@@ -5,7 +5,7 @@
"description": {
"en": "Pleroma package for YunoHost application."
},
"version": "0.0.1~ynh2",
"version": "0.9.0~ynh2",
"url": "",
"license": "free",
"maintainer": {
......@@ -35,7 +35,7 @@
"ask": {
"en": "Give a name for your instance. This will be shown on the tab of the browser"
},
"example": "YUNoHost Pleroma?"
"example": "YUNoHost Pleroma"
},
{
"name": "is_public",
......@@ -58,7 +58,7 @@
"ask": {
"en": "Set the password for the moderator user"
},
"example": "myreallystrongtpassword"
"example": "myreallystrongpassword"
},
{
"name": "instance_user_password_verify",
......@@ -66,7 +66,7 @@
"ask": {
"en": "Type the password for the moderator user again"
},
"example": "myreallystrongtpassword"
"example": "myreallystrongpassword"
},
{
"name": "instance_user_mail",
......
......@@ -21,13 +21,21 @@ domain=$(ynh_app_setting_get $app domain)
path_url=$(ynh_app_setting_get $app path)
is_public=$(ynh_app_setting_get $app is_public)
final_path=$(ynh_app_setting_get $app final_path)
db_name="pleroma_dev"
db_name=$(ynh_app_setting_get $app db_name)
#=================================================
# ENSURE DOWNWARD COMPATIBILITY
#=================================================
# Unused atm
# This can be used in cases where the repo changes between versions
# or if specific setup is needed between certain versions...
# Basically it schould be something like
#
# if (current_version <= specific version) {first do this};
#
# This line can then remain and new lines can be added when needed
# Always assume people can be using any version of the package!
#=================================================
# BACKUP BEFORE UPGRADE THEN ACTIVE TRAP
......@@ -58,7 +66,7 @@ path_url=$(ynh_normalize_url_path $path_url)
su - $app -c "cd $final_path/pleroma;git pull;MIX_ENV=prod mix deps.get;MIX_ENV=prod mix ecto.migrate;"
#=================================================
# RELOAD NGINX
# RESTART PLEROMA
#=================================================
systemctl restart $app
......
Markdown is supported
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