Eternal-Twin

Home | Applications

Eternal-Twin Integration

This section describes how to integrate Eternal-Twin into your project's repository. Integrating Eternal-Twin to your repository allows you to run and test your project using a locally installed version of the Eternal-Twin website.

Eternal-Twin is installed as a project-local Node package:

  • it ensures all the contributors use the same version
  • the project is fully self-contained and does not require an internet connection to run
  • if you have multiple projects on your computer, there are no conflicts: each one has its own Eternal-Twin version.

The packaged version is not the full website (for example, it does not include translations). It's a lightweight version specifically intended to be installed inside other projects.

System requirements

You need the following tools on your system:

Using npm as an alternative to yarn is not officially supported but should work.

Configure your repository for Node packages

Your repository must contain a package.json file at its root. It is a manifest file containing metadata for Node.js.

If your project does not have a package.json, you may create one by running the following command at the repo root and replying to the prompts:

yarn init .

You may read the Yarn or npm documentation if you wish to learn more about package.json files.

Below is an example minimal package.json file.

{
  "name": "myproject",
  "version": "0.0.1",
  "licenses": [
    {
      "type": "AGPL-3.0-or-later",
      "url": "https://spdx.org/licenses/AGPL-3.0-or-later.html"
    }
  ],
  "private": true,
  "scripts": {},
  "dependencies": {},
  "devDependencies": {}
}

Make sure to commit the package.json file.

Install Eternal-Twin inside your project

Run the following command in the directory containing package.json:

yarn add --dev @eternal-twin/website

This will perform the following 3 actions:

  1. Update your package.json file to document the new dependency on the package @eternal-twin/website.
  2. Download the package (and its own dependencies) into the node_modules directory.
  3. Create (or update) a yarn.lock file to remember the exact version of the dependencies that were installed and prevent accidental regressions.

Commit the package.json and yarn.lock files.

Do not commit the node_modules directory: add the node_modules/ rule to your .gitignore file.

You now have to update your package.json file to expose the etwin command. Add the entry "etwin": "etwin" to the scripts config in your package.json. The resulting package.json should be similar to:

{
  "name": "myproject",
  "version": "0.0.1",
  "licenses": [
    {
      "type": "AGPL-3.0-or-later",
      "url": "https://spdx.org/licenses/AGPL-3.0-or-later.html"
    }
  ],
  "private": true,
  "scripts": {
    "etwin": "etwin"
  },
  "dependencies": {},
  "devDependencies": {
    "@eternal-twin/website": "^0.3.1"
  }
}

Configure Eternal-Twin

Before you can run Eternal-Twin, you must configure it.

ℹ There is an open issue to allow Eternal-Twin to run without any configuration file.

The Eternal-Twin configuration is loaded from a file named etwin.toml.

This file may contain configuration specific to your local machine and as such should not be stored in Git. The recommended strategy to configure Eternal-Twin is the following:

  1. Create a file named etwin.toml.example.
  2. Copy the official example configuration (raw) into etwin.toml.example. You do not need to customize the config yet.
  3. Add the etwin.toml rule to your .gitignore, commit the file etwin.toml.example
  4. Update your project setup documentation: contributors should copy the file etwin.toml.example into etwin.toml manually.
  5. Copy your etwin.toml.example file into etwin.toml.

Start Eternal-Twin

Once Eternal-Twin is installed and configured, you can run it from anywhere inside your repo using the following command:

yarn etwin

This command starts the local Eternal-Twin server on your computer. You can use this server to test your project.

When starting, the server displays the configuration it is using. You can use this information to troubleshoot your configuration.

By default, the server uses the port 50320 and is available at the address http://localhost:50320/.

Next steps

Now that your repo is configured to run Eternal-Twin, you may start to actually integrate your project with Eternal-Twin. The first step would be to use Eternal-Twin to manage user accounts through OAuth.