[Markdown]

Collaboration: Home

Collaboration

To make it easier to collaborate on projects, we are setting up a standard server configuration. Not all projects will follow this server setup, but we will try to conform with it as much as possible.

Production and Development Servers

When developing websites, we will typically have two sites, one for development and one for production (i.e. the live website).

Documentation for each project will be kept for project-specific notes. Developers will have access to the projects wiki.

They will be configured as follows:

Development
- Hubzilla Repos
  - Core (master branch)
  - Addons (master branch)
  - Widgets (master branch)
  - Themes (master branch)
- Neuhub Repos
  - Addons (dev branch)
  - Widgets (dev branch)
  - Themes (dev branch)
- Custom (website specific repositories, if used)
  - Addons (dev branch)
  - Widgets (dev branch)
  - Themes (dev branch)
Production
- Hubzilla
  - Core (master branch)
  - Addons (master branch)
  - Widgets (master branch)
  - Themes (master branch)
- Neuhub Repos
  - Addons (main branch)
  - Widgets (main branch)
  - Themes (main branch)
- Custom Repos (website specific repositories, if used)
  - Addons (main branch)
  - Widgets (main branch)
  - Themes (main branch)

The exact location of the custom repos will vary by project, but for most projects, they will reside somewhere in WisTex's GitHub account.

The installation procedures are located here: https://codejournal.dev/wiki/scott/Hubzilla/Installation

Examples and Experimental Code

This includes starter code that you can copy into other development repos.

Although much of the example code will work, none of it is intended to be deployed without significant modifications.

For example, the example code for creating custom pages will be maintained here, as well as various examples of how to create addons, themes, and widgets.

These will be located in: https://github.com/WisTex/Neuhub

The WisTex Repos

These repos include site specific code for various WisTex websites, as well as themes, widgets,and addons used by these websites.

These websites use the WisTex repos instead of the Neuhub repos. And some future websites might still use this setup.

Since there many be naming conflicts, the WisTex repos and Neuhub repos should never be installed on the same website.

Themes like Neuhub Tab will be kept in sync. They will be developed in the Neuhub repo and then copied over to the WisTex repo.

Themes, addons, and widgets that only exist in the WisTex repo will be developed in the WisTex repo.

New sites are unlikely to use this model.

Core Testing

In addition to the installations for testing Neuhub and site specific code, we may need to test changes to the Hubzilla core before they are rolled out. We typically only need to do this if there are specific changes or features we want to test out.

Development
- Hubzilla
  - Core (dev branch or specific RC branch)
  - Addons (dev branch or specific RC branch)
  - Widgets (dev branch or specific RC branch)
  - Themes (dev branch or specific RC branch)
- Neuhub
  - Addons (main branch)
  - Widgets (main branch)
  - Themes (main branch)
- Custom (website specific repositories, if used)
  - Addons (main branch)
  - Widgets (main branch)
  - Themes (main branch)