130 lines
22 KiB
JSON
130 lines
22 KiB
JSON
{
|
||
"0": {
|
||
"id": "0",
|
||
"title": "",
|
||
"content": "404 Page not found :( The requested page could not be found.",
|
||
"url": "https://gancio.org/404.html",
|
||
"relUrl": "/404.html"
|
||
},
|
||
"1": {
|
||
"id": "1",
|
||
"title": "About",
|
||
"content": "About Gancio was born in Italy from political hacking movements, in particular from the hacklab underscore. We deal not only with technology but also with politics because we believe that technology is not neutral, that the Internet can also become an instrument of oppression, that information and software must be free and that knowledge is not for sale. For us, hacking is study and sharing, it is conscious and unconventional use of tools. In 2018 we set up a “radical local server” cisti.org that hosts services explicitly designed for local people / movements / groups / collectives and it is NOT our intention to grow. In fact, we believe that one of the main issues of technology is the scale. We liked very much the idea of the federation and following the example of our brothers and sisters in bologna (the bida.im collective) we setup a mastodon instance as a first service. The next step was to host a shared calendar, but as we didn’t find anything that would fit, we decided to write it ourselves.",
|
||
"url": "https://gancio.org/about",
|
||
"relUrl": "/about"
|
||
},
|
||
"2": {
|
||
"id": "2",
|
||
"title": "Changelog",
|
||
"content": "All notable changes to this project will be documented in this file. 0.20.0 New layout (navbar/footer/visible filters) two month calendar on large display admin could edit title, description, about, favicon & logo directly form admin panel new add event layout => https://demo.gancio.org/add new editor to describe events (bold, italic, link) supported also using copy/paste the editor also support live markdown (try using ### at line start) start oauth2 server implementation (documentation: https://gancio.org/dev/oauth) add fediverse moderation fix embedding an event via iframe images converted in .webp new catalan translation, thanks @fadelkon 0.17.14 [locale] add catalan [fix] fedi outbox 0.17.12 [ui] add admin section on event page in mobile #63 [fix] remove username from users 0.17.11 [refactor] s/fed_user/ap_user [fedi] admin moderation 0.17.10 [refactor] s/comment/resource/ [refactor] remove username field [doc] about and federation 0.17.8 [fix] use thumb in head og:img only 0.17.7 [fix] #58 wrong url for RSS feed 0.17.5 [fedi] comments moderation [fedi] user moderation [fedi] instance moderation [hotfix] cli setup [doc] fix debian upgrade [fix] comment ap_id key length [fix] fediverse signature [fedi] better /inbox /followers response 0.17.0 [feat] add rss link @homepage [ui] add lot of explanation text [ui] show copied messages [admin] show n of unconfirmed users/events [ui] spinner while event image is loading [fedi] add follow me dialog in event [fix] do not add reminders in full ics export [fix] remove spaces from hashtags sent via AP [fix] #56 unconfirmed event sent via ap [fix] localPosts/comments in fediverse stats 0.16.0 [feat] embed event as widget in external website [fedi] instances moderation in admin [fix] toggle event visibility by owner [fedi] manage unboost [refactoring] auth as middleware 0.15.7 [fix] minor 0.15.6 [fix] tags in event 0.15.5 [model] migrations setup [feat] embeddable event widget/iframe 0.15.2 [fix] delete event [fix] wrong html hierarchy 0.15.0 [fix] backtop icon on mobile [fix] webfinger nodeinfo return real node info [fix] register email confirmation [feat] add federation settings (enable comments/boost/like) [feat] new event page layout [feat] could download .ics of event [feat] add cors to feed requests [refactoring] settings middleware, cleaning codebase 0.14.18 [improve] better quality for images [fix] password recovery email [feat] new action field for notification [feat] add DEBUG env variable in docker-compose.yml [style] fixed width in confirmation events table [fix] #38 timezone issue in rss export and using tor… 0.14.17 [fix] image previews from external website [fix] docker-compose postgresql docs [improve] export white logo to fediverse",
|
||
"url": "https://gancio.org/changelog",
|
||
"relUrl": "/changelog"
|
||
},
|
||
"3": {
|
||
"id": "3",
|
||
"title": "Configuration",
|
||
"content": "Configuration Main gancio configuration is done with a configuration file. This shoud be a .json or a .js file and could be specified using the --config flag. eg. gancio start --config ./config.json eg. pm2 start gancio start -- --config ~/config.json Title Description BaseURL Server Database Upload path SMTP Admin_email Favicon User locale Secret Default settings Title The title will be in rss feed, in html head and in emails: "title": "Gancio" Description "description": "a shared agenda for local communities" BaseURL URL where your site will be accessible (include http or https): "baseurl": "https://gancio.cisti.org" Server This probably support unix socket too :D "server": { "host": "localhost", "port": 13120 } Database DB configuration, look here for options. "db": { "dialect": "sqlite", "storage": "/tmp/db.sqlite" } Upload path Where to save images "upload_path": "./uploads" SMTP SMTP configuration. Gancio should send emails at following events: the admin should receive emails of anon event (if enabled) to confirm them. the admin should receive emails of registration request (if enabled) to confirm them. an user should receive an email of registration requested. an user should receive an email of confirmed registration. an user should receive a confirmation email when subscribed directly by admin. "smtp": { "auth": { "user": "", "pass": "" }, "secure": true, "host": "" } Admin_email Email of administrator. Note that email from gancio comes from this email and that the SMTP configuration above should allow to use this address as from. Favicon You could specify another favicon. This is also used as logo (top-left corner): "favicon": "./favicon.ico" User locale Probably you want to modify some text for your specific community, that’s why we thought the user_locale configuration: you can specify your version of each string of gancio making a directory with your locales inside. For example, let’s say you want to modify the text inside the /about page: mkdir /opt/gancio/user_locale put something like this in /opt/gancio/user_locale/en.js to override the about in english: export default { about: 'A new about' } and then point the user_locale configuration to that directory: "user_locale": "/opt/gancio/user_locale" Watch here for a list of strings you can override. :warning: Note that a restart is needed when you change user_locale’s content. Secret Default settings { "title": "Gancio", "description": "A shared agenda for local communities", "baseurl": "http://localhost:13120", "server": { "host": "0.0.0.0", "port": 13120 }, "db": { "dialect": "sqlite", "storage": "/tmp/db.sqlite" }, "upload_path": "./", "favicon": "../dist/favicon.ico", "smtp": { "auth": { "user": "", "pass": "" }, "secure": true, "host": "" }, "admin_email": "", "secret": "notsosecret" }",
|
||
"url": "https://gancio.org/config",
|
||
"relUrl": "/config"
|
||
},
|
||
"4": {
|
||
"id": "4",
|
||
"title": "Contacts",
|
||
"content": "Contacts :elephant: Mastodon ⇒ @gancio@mastodon.cisti.org",
|
||
"url": "https://gancio.org/contacts",
|
||
"relUrl": "/contacts"
|
||
},
|
||
"5": {
|
||
"id": "5",
|
||
"title": "Debian",
|
||
"content": "Debian installation Install Node.js & yarn (from root) curl -sL https://deb.nodesource.com/setup_12.x | bash - apt-get install -y nodejs curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - echo "deb https://dl.yarnpkg.com/debian/ stable main" > /etc/apt/sources.list.d/yarn.list apt-get update && apt-get install yarn source Install Gancio yarn global add gancio --prod Setup with postgreSQL (optional as you can choose sqlite) apt-get install postgresql # Create the database su postgres -c psql postgres=# create database gancio; postgres=# create user gancio with encrypted password 'gancio'; postgres=# grant all privileges on database gancio to gancio; Create a user to run gancio from adduser gancio su gancio Launch interactive setup gancio setup --config config.json Start gancio start --config config.json Point your web browser to http://localhost:13120 or where you selected during setup. Setup nginx as a proxy To deploy gancio in production you should use something like pm2: sudo yarn global add pm2 pm2 start gancio -- --config config.json # Run this command to run your application as a service and automatically restart after a reboot: pm2 startup # read the output! sudo pm2 startup -u gancio Upgrade sudo yarn global add gancio sudo service pm2 restart",
|
||
"url": "https://gancio.org/install/debian",
|
||
"relUrl": "/install/debian"
|
||
},
|
||
"6": {
|
||
"id": "6",
|
||
"title": "Hacking",
|
||
"content": "Development Stack Gancio is built with following technologies: Nuxt.js Vue.js Express Node.js Sequelize Element.ui Testing on your own machine Download source git clone https://framagit.org/les/gancio Install dependencies yarn Hacking yarn dev Please use the issue board and the forum to discuss any modification.",
|
||
"url": "https://gancio.org/dev",
|
||
"relUrl": "/dev"
|
||
},
|
||
"7": {
|
||
"id": "7",
|
||
"title": "Docker",
|
||
"content": "Initial setup Use sqlite Use postgreSQL Start gancio Upgrade Initial setup You do not need to clone the full repo as we distribute gancio via npm. A Dockerfile and a docker-compose.yml are the only files needed. Create a directory where everything related to gancio is stored (db, images, config) mkdir /opt/gancio cd /opt/gancio note that you can choose a different directory. Use sqlite Download docker-compose.yml and Dockerfile wget https://gancio.org/docker/Dockerfile wget https://gancio.org/docker/sqlite/docker-compose.yml Create an empty db and config (this is needed) touch config.json db.sqlite mkdir user_locale Build docker image and launch interactive setup in one step docker-compose build docker-compose run --rm gancio gancio setup --docker --db=sqlite Use postgreSQL Download docker-compose.yml and Dockerfile wget https://gancio.org/docker/Dockerfile wget https://gancio.org/docker/postgres/docker-compose.yml Create an empty configuration (this is needed) touch config.json mkdir user_locale Build docker image and launch interactive setup in one step docker-compose build docker-compose run --rm gancio gancio setup --docker --db=postgres Start gancio Run your container docker-compose up -d Look at logs with docker-compose logs Setup nginx as a proxy Point your web browser to http://localhost:13120 or where you specified during setup and enjoy :tada: You can edit config.json file and restart the container on your needs, see Configuration for more details. Upgrade cd /opt/gancio docker-compose up -d --no-deps --build",
|
||
"url": "https://gancio.org/install/docker",
|
||
"relUrl": "/install/docker"
|
||
},
|
||
"8": {
|
||
"id": "8",
|
||
"title": "Federation",
|
||
"content": "Federation Each instance has only one AP Actor that publishes each event. We are considering the introduction of other “Actor” but they will not be linked to users, rather to places or tags/categories. There are no personal homes with a timeline of people I follow, everyone has a sort of local timeline of the instance, it’s an anti filter-bubble feature. Events are not published with the type Event but with type Note because we wanted to add the possibility to interact with events from mastodon instances (boost / bookmark and “comments” that we call resources because we don’t want it to become a place of debate, but more a place where to keep a historical memory of events, e.g. an audio recording of a talk). When mastodon will support Event object type we will change for sure.",
|
||
"url": "https://gancio.org/federation",
|
||
"relUrl": "/federation"
|
||
},
|
||
"9": {
|
||
"id": "9",
|
||
"title": "Home",
|
||
"content": "ancio A shared agenda for local communities. Get started now Demo Source Some relevant key features: Focus on content not on people: nowhere on gancio appears the identity of who published the event, not even under a nickname, not even to administrators (except in the db). This is not an ego-friendly platform. Visitors first. We do not want logged user to get more features than random visitor. We do not want users to register, except to publish events and even in this case you can publish an anonymous event. Anonymous events: optionally a visitor can create events without being registered (an administrator has to confirm them) We are not interested in making hits so we export events in many ways, via RSS feeds, via global or individual ics, incorporating lists of events or single event via iframe on other websites and via AP Very easy UI Multidays events support (festival, conferences…) Recurrent events support (each monday, each two monday, each monday and friday, each two saturday, etc.) Filters events for tags or places RSS and ICS export (with filters) embeddable iframe (example) boost / bookmark / comment events from the fediverse! Lot of configurations available (user registration open/close, enable federation, enable recurrent events) License Gancio is distributed by an AGPL-3.0 Licence.",
|
||
"url": "https://gancio.org/",
|
||
"relUrl": "/"
|
||
},
|
||
"10": {
|
||
"id": "10",
|
||
"title": "Install",
|
||
"content": "Install (production) Install on Debian Install using docker Post installation Nginx as a proxy If you wanna hack or run the current develop release take a look at Hacking & contribute",
|
||
"url": "https://gancio.org/install",
|
||
"relUrl": "/install"
|
||
},
|
||
"11": {
|
||
"id": "11",
|
||
"title": "Instances",
|
||
"content": "Instances gancio.cisti.org (Turin, Italy) lapunta.org (Florence, Italy) chesefa.org (Naples, Italy) Do you want your instance to appear here? Write us.",
|
||
"url": "https://gancio.org/instances",
|
||
"relUrl": "/instances"
|
||
},
|
||
"12": {
|
||
"id": "12",
|
||
"title": "Internationalization",
|
||
"content": "Internationalization We’re self-hosting an instance of weblate you can use to help us with translations.",
|
||
"url": "https://gancio.org/dev/locales",
|
||
"relUrl": "/dev/locales"
|
||
},
|
||
"13": {
|
||
"id": "13",
|
||
"title": "Nginx",
|
||
"content": "Nginx proxy configuration This is the default nginx configuration for gancio, please modify at least the server_name and ssl_certificate’s path. Note that this does not include a cache configuration and that gancio does not use a cache control at all, if you can help with this task you’re welcome. server { listen 80; listen [::]:80; server_name gancio.cisti.org; root /var/www/letsencrypt; location /.well-known/acme-challenge/ { allow all; } location / { return 301 https://$host$request_uri; } } server { listen 443 ssl http2; listen [::]:443 ssl http2; server_name gancio.cisti.org; ssl_protocols TLSv1.2; ssl_ciphers HIGH:!MEDIUM:!LOW:!aNULL:!NULL:!SHA; ssl_prefer_server_ciphers on; ssl_session_cache shared:SSL:10m; # Uncomment these lines once you acquire a certificate: # ssl_certificate /etc/letsencrypt/live/gancio.cisti.org/fullchain.pem; # ssl_certificate_key /etc/letsencrypt/live/gancio.cisti.org/privkey.pem; keepalive_timeout 70; sendfile on; client_max_body_size 80m; gzip on; gzip_disable "msie6"; gzip_vary on; gzip_proxied any; gzip_comp_level 6; gzip_buffers 16 8k; gzip_http_version 1.1; gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript; add_header Strict-Transport-Security "max-age=31536000"; location / { try_files $uri @proxy; } location @proxy { proxy_set_header Host $host; proxy_set_header X-Forwarded-Proto https; proxy_set_header Proxy ""; proxy_pass_header Server; proxy_pass http://127.0.0.1:13120; proxy_buffering on; proxy_redirect off; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; tcp_nodelay on; } }",
|
||
"url": "https://gancio.org/install/nginx",
|
||
"relUrl": "/install/nginx"
|
||
},
|
||
"14": {
|
||
"id": "14",
|
||
"title": "OAuth",
|
||
"content": "BETA FEATUREExpect bad behavior and open issues OAuth An open standard for token-based authentication and authorization on the Internet. Gancio supports OAuth 2.0, an authorization framework described in RFC 6749 that allows third-party applications to obtain limited access to an HTTP service on behalf of a resource owner, through the use of a standardized authorization flow that generates a client access token to be used with HTTP requests. To obtain an OAuth token for a Gancio instance, make sure that you allow your users to specify the domain they want to connect to before login. Use that domain to acquire a client id/secret and then proceed with normal OAuth 2. Create client Create a new application to obtain OAuth2 credentials. POST /api/client Request parameters client_name string A name for your application redirect_uris string Where the user should be redirected after authorization scopes string Space separated list of scopes. If none is provided, defaults to event:write as it’s the only supported scope! website string A URL to the homepage of your app Example curl -X POST -d 'client_name=Wordpress Event Manager' -d 'redirect_uris=https://noblogs.org/' -d 'website=https://myapp.example' http://localhost:13120/api/client Returns Application, with client_id and client_secret { "name" : "Wordpress Event Manager", "scopes" : "event:write", "website" : "https://myapp.example", "client_secret" : "909029fa12797e6bdfb5baf5e379675dfa4e3ad4", "redirect_uris" : "https://noblogs.org", "client_id" : "0f377e34b2aaf517f7db534f32d26b0dd938fb6d" } List of scopes event:write Grant access to add/update events. Authorize a user Displays an authorization form to the user. If approved, it will create and return an authorization code, then redirect to the desired redirect_uri. The authorization code can be used while requesting a token to obtain access to user-level methods. GET /authorize Request parameters response_type string Should be set equal to code redirect_uri string Where the user should be redirected after authorization scope string Should be event:write client_id string client_id, obtained during app registration. Obtain a token POST /oauth/token Request parameters client_id string client_id obtained during client registration client_secret string client_secret obtained during client registration scope string Should be event:write grant_type string Set equal to authorization_code code string A user authorization code, obtained via /authorize",
|
||
"url": "https://gancio.org/dev/oauth",
|
||
"relUrl": "/dev/oauth"
|
||
},
|
||
"15": {
|
||
"id": "15",
|
||
"title": "Recurrent events",
|
||
"content": "Gancio supports recurrent events if enabled to (Admin > Settings, disabled by default). When enabled, you are able to create recurrent events. Recurrent events are not shown by default to visitors, they have to enable it, or you can choose to show them by default in admin panel. Add a recurrent event Same as adding a normal event, but you can choose choose the details of event recurrence. Choose a frequency first: and use the calendar to select one or more days. How does it work Behind the scene, gancio ensures that at least the next three occurrences of the event are always created. It creates that single events by copying the properties of the parent event, so if you modify the parent event’s title, or the day of the week, each newly created occurrence will took the new title and the new selected day. Old occurrences will be preserved. You can edit a specific event occurrence with more details, a different poster/flyer, a different title/description or decide to completely hide it. Stop/pause a recurrent event (eg. during summer) A specific menu is shown viewing an instance of recurrent event…",
|
||
"url": "https://gancio.org/usage/recurrent",
|
||
"relUrl": "/usage/recurrent"
|
||
},
|
||
"16": {
|
||
"id": "16",
|
||
"title": "Project Structure",
|
||
"content": "Project structure API / backend Client / frontend Federation / ActivityPub API / backend Source code inside server/api/. index.js is basically a routing table pointing each PATH with specified HTTP VERB to a method of a controller. jwt is used to authenticate api request. Express.js is based on middleware, passing each request to a chain of methods. If you come from a PHP background, note that the main difference with Node.js is that the server process is always running and able to manage multiple requests and tasks together (asyncronically) while each php process is tied to a single request. Sequelize is used as ORM. Take a look in /server/api/models. Client / frontend Nuxt.js is used here! Nuxt is basically Vue plus SSR (Server Side Rendering). Client routing in nuxt is automatic (if you don’t need something special), just put your page inside pages and that’s it! Federation / ActivityPub Code inside server/federation.",
|
||
"url": "https://gancio.org/dev/structure",
|
||
"relUrl": "/dev/structure"
|
||
},
|
||
"17": {
|
||
"id": "17",
|
||
"title": "Usage",
|
||
"content": "Usage ehmmm, help needed here :smile: feel free to send a PR => here",
|
||
"url": "https://gancio.org/usage",
|
||
"relUrl": "/usage"
|
||
}
|
||
|
||
}
|