Powerful project collaboration features

Содержание:

Operation and upgrading

My OpenProject instance is slow but my RAM isn’t fully used. What can I do?

Set a higher number of web workers to allow more processes to be handled at the same time. Find out more here and about system requirements here.

I don’t receive emails. Test email works fine but not the one for work package updates.

Use a browser to call your domain name followed by “health_checks/all” (e.g. https://myopenproject.com/health_checks/all). There should be entries about “delayed_jobs_backed_up” and “delayed_jobs_never_ran”. If PASSED is written behind it, everything is good.

If the health check does not return satisfying results, have a look if the background worker is running by entering on the server. If it is not running, no entry is returned. If it is running an entry with “jobs:work” at the end is displayed.

If the worker is not running please try a restart with . If that doesn’t help it could be that the worker is scaled to 0 for some reason, so please try . If that doesn’t help either, please have a look at your logs, which are accessible with .

Another approach would be to restart OpenProject completely, especially after changing the configuration of your SMTP server: .

For some updates of OpenProject, the database layout needs to be adapted to support new features and fix bugs. These changes need to be carried out as part of the update process. This is why it is important to always run as part of the update process.

Please also have a look at our upgrade guide.

Are you using the packaged installation or are you running OpenProject using docker? If the former you may have to run . Leave everything the same but select git integration.

Once that’s done all you have to do is enable automatic creation under /settings/repositories (Administration -> System Settings -> Repositories) and enable repositories by default under Administration -> System Settings -> Projects in the project modules if you want new projects to automatically get a git repository.

For existing projects you can enable the module in the project settings (Project Settings -> Modules) and then configure the repository under Project Settings -> Repository where you choose git and then “Git repository integrated into OpenProject”.

Mind, that repository integration in the sense that you will be able to checkout the repository through OpenProject does only work in the packaged installation, not docker.

Contributor code of conduct

As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.

We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, age, or religion.

Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. Project maintainers who do not follow the Code of Conduct may be removed from the project team.

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers.

This code of conduct is adapted from the Contributor Covenant, version 1.0.0, available at http://contributor-covenant.org/version/1/0/0/

Project dashboard

In order to manage your projects successfully, you should make sure to be up to date about the status at all times. This allows you to keep the project on track and in case to readjust quickly. OpenProject’s project overview is a single dashboard page with important project information. You can display relevant information for your team, such as members, news, project description, work package reports, or a project status. You can add project information as widgets to the dashboard and not only order but also re-size the widgets according to your needs. Furthermore, you can add text widgets, custom texts, links and other information to your overview page.

We included quite a few links to our documentation in this article which also entails videos to make to easier for you to discover how to use OpenProject. If you would like to discover more videos, please check out the OpenProject YouTube channel.

Generate the plugin

You can generate a new plugin directly from OpenProject. Think of a good name and a place (in your filesystem) where the plugin should go. In this example, we have a directory right next to the directory. Then do

This generates the plugins into the directory . The new plugin is a rails engine, which can be published as a gem.

You may want to update the generated plugin’s gemspec ().

Example Plugin

There is an example plugin which does some of the basic things (adding menu items, hooking into views, defining a project menu, etc.) and provides further info in its README.

Instead of generating a new plugin you can also just clone the example plugin and adapt it.

Information Security and Compliance

OpenProject cloud environment are hosted on a logically isolated virtual cloud at Amazon Web Services with all services being located in Europe. AWS is a GDPR compliant cloud infrastructure provider with extensive security and compliance programs as well as unparalleled access control mechanisms to ensure data privacy. Employed facilities are compliant with the ISO 27001 and 27018 standards.

OpenProject cloud environment is continuously backing up user data with data at rest being fully encrypted with AES-256. Each individual instance is logically separated and data is persisted in a unique database schema, reducing the risk of intersection or data leaks between instances.

Production infrastructure is accessible only for a strict set of authorized system operations personnel from a secure internal maintenance VPN. Services employed by employees are secured by Two-factor-authentication where available. Access to customer data is performed only when requested by the customer (i.e., as part of a support or data import/export request).

All OpenProject GmbH employees employ industry standard data security measurements to secure their devices and access to cloud and on-premises infrastructure. All sensitive user data on laptops and workstations are encrypted and machines are maintained to receive system updates.

Steps to release a plugin

The following steps are necessary to release a new plugin:

Code Review

A code review should check the whole code and remove glitches like:

  • Inappropriate comments
  • Deactivated code
  • Minor cases of code smell

Resolve licensing and copyright issues

  1. Check the license and the copyright of the plugin to be released

Usually, this should be GPLv3 and we are the copyright owner. However, some plugins might have additional authors or might originate from code with a different license. These issues have to be resolved first. Also check the years in the copyright. If you need to find all contributors of a repository including their contribution period use the following rake task:

  1. Add a copyright notice to all the source files

There is a rake task in the core to perform this job. Use (e.g. ) to add the copyright header in to all relevant plugin files. If no such file exists, from the core is used.

  1. Check for existence of and if referenced by the copyright notice.

Complete the readme file or add one if not existing

There should be a file README.md containing:

  1. A description about what the plugin is actually doing
  2. Requirements to use the plugin
  3. Instructions how to install and uninstall a plugin
  4. Notes where to report bugs
  5. Notes where to contribute
  6. Credits

If you’re unsure about if/who to give credit, you should take a look into the changelog:

For your convenience you may use the following rake task, that extracts all authors from a repository

  1. Licensing information. It is probably best to use READMEs of already released plugins as a template.

Complete the gemspec

  1. Add the license to the gemspec of the plugin if not already there.
  2. Add any files that should be included to the gemspec (e.g. the folder, the folder if there are any migrations, the , and the ).
  3. Check authors and email point to the right authors.
  4. The homepage should be the homepage of the plugin.
  5. Check if summary and description are there.
  6. Check if all dependencies are listed (this might be difficult, I know): There should be a sentence in the README, that this is an OpenProject-Plugin and requires the core to run. Apart from that, state only dependencies that are not already present in core.
  7. While you are at it, also check if there is any wiring to core versions necessary in engine.rb; also check, that the url of the plugin is wired correctly.
  8. Push the version of the plugin, mostly by just removing any .preX specials at the end.
  9. Don’t forget to add a changelog entry.
  10. Commit everything.
  11. Also create a release tag (named ‘release/<version>’ for example ‘release/1.0.2′) to name the new version.
  12. Push the tag with .

Publish the gem at Rubygems

  • Ensure gemspec fields are complete and version number is correct
  • . This asks for your user/password
  • Go to https://rubygems.org, log in, go to the dashboard, click on the uploaded gem, click edit. Set URLs, at least source code URL and Bug Tracker URL
  • You are done .
  • Be careful when publishing a gem.Once it is published, it cannot be replaced in the same version. It is only possible to take a version out of the index and publish a new version.

Create public visibility

  1. Make the github repository public.
  2. Make the plugin project public. Do a little cleanup work first by removing modules not needed. Currently, Activity, Issue Tracking, Time Tracking, Forums, and Backlogs are default. Also, the My Project Page should only show Project Description and Tickets blocks.
  3. Create a news article about the newly released plugin and its features.
  4. Twitter with a link to the news article.
  5. If the plugin is referenced in our feature tour, add a download link to the plugin in the feature tour

Frontend plugins

Plugins that extend the frontend application may be packaged as npm modules. These plugins must contain a in the root directory of the plugin.

Plugins are responsible for loading their own assets, including additional images, styles and I18n translations.

Translations are processed by I18n.js through Rails and will be picked up from .

Pure frontend plugins are currently not possible without modifications to the OpenProject core . We instead recommend to create a hybrid gem plugin instead (see below).

Onboarding variables:

Enterprise Limits

If using an Enterprise token there are certain limits that apply. You can configure how these limits are enforced.

default: false

If you set to true, new users cannot be invited or registered if the user limit has been reached. If it is false then you can still invite and register new users but their activation will fail until the user limit has been increased (or the number of active users decreased).

Configured in the like this:

Or through the environment like this:

Backup enabled

default: true

If enabled, admins (or users with the necessary permission) can download backups of the OpenProject installation via OpenProject’s web interface or via the API.

There are further configurations you can use to adjust your backups.

Per default the maximum overall size of all attachments must not exceed 1GB for them to be included in the backup. If they are larger only the database dump will be included.

As usual this can be override via the environment, for example like this:

Show community links

If you would like to hide the homescreen links to the OpenProject community, you can do this with the following configuration:

Security badge

OpenProject now provides a release indicator (security badge) that will inform administrators of an OpenProject installation on whether new releases or security updates are available for your platform.

If enabled, this option will display a badge with your installation status at Administration > Information right next to the release version, and on the home screen. It is only displayed to administrators.

The badge will match your current OpenProject version against the official OpenProject release database to alert you of any updates or known vulnerabilities. To ensure the newest available update can be returned, the check will include your installation type, current version, database type, enterprise status and an anonymous unique ID of the instance. To localize the badge, the user’s locale is sent. No personal information of your installation or any user within is transmitted, processed, or stored.

To disable rendering the badge, uncheck the setting at Administration > System settings > General or pass the configuration flag .

Ошибки

OpenProj не поддерживается более 10 лет. Программное обеспечение Serena ранее выдавало предупреждение и предлагало пользователям использовать ProjectLibre. Начиная с версии 1.4, ошибки в программном обеспечении обычно проявляются только для пользователей, которые пытаются использовать более продвинутые функции. Например, задачи могут таинственным образом запускаться в определенное время (они ведут себя так, как будто у них есть ограничение «Начать не раньше, чем», даже если его нет, и дата начала проекта не является ограничением), ссылки показывают пробелы, фиксированная стоимость для сводки задачи не суммируются, не редактируются и т. д. Иногда эти ошибки решаются перезапуском программы, но другие сохраняются.

По сравнению с Microsoft Project, который он полностью имитирует, OpenProj имеет аналогичный пользовательский интерфейс (UI) и похожий подход к построению плана проекта: создание списка задач с отступом или иерархической структуры работ (WBS), установка продолжительности, создание ссылок ( либо (а) перетаскивая мышью, (б) выбирая, а затем нажимая кнопку, или (в) вручную набирая в столбце «предшественник»), назначьте ресурсы. Столбцы (поля) такие же, как и в Microsoft Project. Пользователи одного из программ должны в целом чувствовать себя комфортно при использовании другого. Затраты такие же: оплата труда, почасовая оплата, использование материалов и постоянные затраты: все это предусмотрено.

Однако есть небольшие различия в пользовательском интерфейсе (комментарии относятся к версии 1.4), которые требуют некоторой адаптации для тех, кто знаком с Microsoft Project, т.е. OpenProj не может связываться вверх с методом (c), вставка задач сложнее, чем в Microsoft Project. , а OpenProj не может создавать ресурсы «на лету» (их нужно сначала создать на листе ресурсов). У OpenProj также есть несколько более серьезных ограничений, главным из которых является отсутствие более подробных представлений и отчетов, типичных для Microsoft Project. Например, хотя поля существуют для стоимости, нет быстрого способа показать их, кроме как вручную вставить их. Для этого требуется относительно продвинутый пользователь: кто-то, кто знает, как могут называться поля и как их использовать.

История и статус

Марк О’Брайен, Ховард Кац и Лоран Кретьенно разработали OpenProj в компании Projity в 2007 году. Он вышел из бета-версии с версией 1.0 10 января 2008 года.

В конце 2008 года Projity была приобретена Silver Lake Partners (частной инвестиционной компанией) через свою тогдашнюю дочернюю компанию Serena Software .

В ноябре 2008 года поддержка и развитие OpenProj оказались приостановленными. Несколько более поздних коммитов в CVS с регрессами, но без улучшений. Он больше не совместим с Microsoft Project.

Serena / Projity также разработала программное обеспечение для проектов « Программное обеспечение как услуга» (SaaS), Projects On Demand. (Услуга «Проекты по запросу» закончилась 11 июня 2011 г.)

В 2012 году основатели OpenProj объявили, что они разделили кодовую базу OpenProj и начали другую реализацию.

Серена объявила и разместила в Интернете, чтобы избежать загрузки OpenProj и вместо этого загрузить ProjectLibre .

Первоначальный выпуск ProjectLibre состоялся в августе 2012 года. ProjectLibre был полностью переписан и, таким образом, технически перестал быть форком.

Step 3: Apache2 web server

OpenProject comes with an internal ruby application server, but this server only listens on a local interface. To receive connections from the outside world, it needs a web server that will act as a proxy to forward incoming connections to the OpenProject application server.

This wizard step allows you to auto-install an Apache2 web server to function as that proxy.

The available options are:

Install Apache2 web server (default)

We recommend that you let OpenProject install and configure the outer web server, in which case we will install an Apache2 web server with a VirtualHost listening to the domain name you specify, optionally providing SSL/TLS termination.

In case you select to auto-install Apache2, multiple dialogs will request the parameters for setting it up:

Domain name

Server path prefix

If you wish to install OpenProject under a server path prefix, such as , please specify that prefix here with a leading slash. For example: . If OpenProject should respond to as specified in the previous dialog, simply leave this dialog empty and confirm by pressing .

SSL/TLS configuration

OpenProject can configure Apache to support HTTPS (SSL/TLS). If you have SSL certificates and want to use SSL/TLS (recommended), select Yes.

In that case, you will be shown three additional dialogs to enter the certificate details:

  1. The absolute SSL certificate path
  2. The absolute SSL private key path
  3. The path to the Certificate Authority bundle for the certificate (optional, leave empty unless needed)

External SSL/TLS termination

If you terminate SSL externally before the request hits the OpenProject server, you need to follow the following instructions to avoid errors in routing. If you want to use SSL on the server running OpenProject, skip this section.

If you have a separate server that is terminating SSL and only forwarding/proxying to the OpenProject server, you must select “No” in this dialog. However, there are some parameters you need to put into your outer configuration.

  • If you’re proxying to the openproject server, you need to forward the HOST header to the internal server. This ensures that the host name of the outer request gets forwarded to the internal server. Otherwise you might see redirects in your browser to the internal host that OpenProject is running on.
    • In Apache2, set the directive
    • In NginX, use the following value:
  • If you’re terminating SSL on the outer server, you need to set the header to let OpenProject know that the request is HTTPS, even though its been terminated earlier in the request on the outer server.
    • In Apache2, use
    • In Nginx, use
  • Finally, to let OpenProject know that it should create links with ‘https’ when no request is available (for example, when sending emails), you need to set the following setting: followed by an . This ensures that OpenProject responds correctly with secure cookies even though it was not configured for https in the server configuration.

Skip (not recommended)

The installer will not set up an external web server for accessing. You will need to either install and set up a web server such as Apache2 or Nginx to function as the web server forwarding to our internal server listening at by proxying.

Only choose this option if you have a local Apache2 installed that the OpenProject package may not control, or need to use a different web server such as Nginx. Please note that not all functionality (especially regarding Repositories) are supported on Nginx.

When installing with an existing Apache2, you can take a look at the source of our installation templates for guidance on how to set up the integration.

Here’s an exemplary configuration that might work for you.

For a minimal nginx config, please see this gist as as starting point.

Please note: If you reconfigure the OpenProject application and switch to , you might run into errors with the Apache configuration file, as that will not be automatically remove. Please double-check you removed references to the if you do reconfigure.

All-in-one container

Quick Start

The fastest way to get an OpenProject instance up and running is to run the following command:

This will take a bit of time the first time you launch it, but after a few minutes you should see a success message indicating the default administration password (login: , password: ).

You can then launch a browser and access your new OpenProject installation at http://localhost:8080. Easy!

To stop the container, simply hit CTRL-C.

Note that the above command will not daemonize the container and will display the logs to your terminal, which helps with debugging if anything goes wrong. For normal usage you probably want to start it in the background, which can be achieved with the flag:

Note: We’ve had reports of people being unable to start OpenProject this way because of an and permissions to write to . If you run into this, a workaround seems to be to add to your run command, even if you run in detached mode.

Organize and visualize your project

Projects vary and require a different view by project. Depending on what type of project you are managing, you might want to use a work package list view, agile boards, Gantt chart, backlogs, task board or a roadmap. OpenProject offers both traditional and agile project management and even allows to combine both to a hybrid project management approach.

We would like to show you the major OpenProject modules that offer different project views. However, as mentioned, you can also combine them.

Work package view

Work packages are the base for your project collaboration in OpenProject. They are items in a project (such as tasks, features, risks, user stories, bugs, change requests) and capture various additional attributes, such as status, assignee, priority, due date. The shows all work packages in a list with selected attributes in the columns. You can customize the view by filtering by attributes and choosing the attributes shown in the columns.

Gantt chart

The displays the work packages in a timeline. You can collaboratively create and manage your project plan. Have your project timelines available for all team members and share up-to-date information with stakeholders. You can add start and finish date and adapt it with drag and drop in the Gantt chart. Also, you can add dependencies, predecessor or follower within the Gantt chart.

Agile Boards

Boards support agile project management methodologies, such as Scrum or Kanban. Our agile boards can be for anything you would like to keep track of within your projects: Tasks to be done, Bugs to be fixed, Things to be reviewed, Features to be developed, Risks to be monitored, Ideas to be spread, anything! The boards consist of lists (columns) and cards. You can choose between a basic board and various action boards. The following board shows a Kanban example where you move your work packages from one status to the next. If you want to find out more about the different agile boards , please click .

Backlogs

The starting point for effective work in Scrum teams is a well-maintained and prioritized product backlog as well as the creation of sprint backlogs. In OpenProject, you can easily record and specify requirements represented by user stories. Moreover, you can respond to inquiries and sort them by priority for implementation.

Task Board

To support daily scrum meetings, all of a team’s tasks and sprint impediments are recorded in a digital task board. The digital task board thus allows team members to get a fast overview of the current state of a sprint.

Roadmap

Share your product roadmap with your stakeholders, get feedback about your ideas and break it down into a detailed release plan. In the roadmap, you can see all work packages and their status listed by versions at a glance. For each version, the related work package can be assessed from the list displayed in the roadmap view. Subjects which are crossed out represent closed work packages.

Open an existing project

In order to open an existing project, click the Select a project button in the upper left corner of the header and select the project you want to open.

You can also start typing in a project name to filter by the project’s title.

Projects and subprojects are displayed according to their hierarchy in the drop-down menu.

Subproject is defined as a child project of another project. Subprojects can be used to display a hierarchy of projects. Several filter options (e.g. in work package list and timeline) can be applied only to the current project and its subprojects.

Also, you will see your newest projects on the application landing page in the Projects section. Here you can simply click on one of the newest visible projects to open it.

What is new in OpenProject 11.0?

Top-down project scheduling with new manual planning mode

Top-down scheduling enables the project team to define all tasks involved in a project, starting with a fixed start and finish date, and breaking it down into smaller work packages. The new manual scheduling mode in OpenProject allows to set a start and finish date of the parent without being affected by the start and finish dates of its children. You can now plan a project top-down without knowing all tasks at the start of the project.

Moving a child element in the manual scheduling mode will not move the dates of the parent element. It will now indicate the scheduling differences with a blue or red bracket underneath (e.g. when a child is shorter or longer than the parent phase). Also, we have added a grey background on hover to indicate the parent-child-relationships.

Now, in OpenProject you can rely on both, top-down and bottom-up planning or even a combination of both. The approach you choose depends on your specific planning goal.

Versatile agile boards give you more options (premium feature)

The new board types in OpenProject allow you even more flexible agile project management. Now, you can create a work breakdown structure for your project by adding parent-child-elements as a board. Select the parent work packages from the list and create a board with all corresponding children work packages.

WBS (work-breakdown-structure) boards

Agile boards for subprojects

Also, project hierarchies can now be displayed in the boards, e.g. to distribute tasks between subprojects. Subprojects can be selected as lists.

New boards creation screen to select different board types

Furthermore, we have implemented more improvements to the agile boards, such as a better board creation modal. It is now much easier to choose a new board from the available options.

Cards with details view in boards

To get more information about the cards in a board and to enable quick and easy updates of all work package attributes incl. custom fields, we have enabled a split-screen view also for the boards view. The new split screen view can be enabled via the info icon on the cards.

Project templates for easy project creation

The new project templates allow you to create projects based on predefined templates. When setting up a project you can define whether this project should be used as a project template. You will then have the possibility to select a predefined project template when creating a new project which already includes all configurations, e.g. assignee, project plan, work breakdown structure.

Improved project portfolio management

The configuration of the “view all projects” page now enables better project portfolio management. You can configure the “view all projects” list to show relevant project information for all projects, e.g. add custom fields for projects and remove columns which are not needed. With the link to the Gantt charts view you can directly open a global work packages view for all projects, configured to your needs, e.g. to show all milestones across all projects.

Harmonization of the time and costs modules

Tracking spent time and costs is now much easier with the improved and harmonized modules for time and cost reporting. The modules Time tracking and Cost reporting have been combined. Whenever you want to track time and/or costs in a project, the new module Time and costs needs to be activated in the project settings. It automatically adds the time tracking and cost reporting functionality to the project. The Budgets module will remain unchanged and additionally enables project budgets to be tracked.

Improvements of the WYSIWYG editor

We have again added many improvements to the WYSIWYG editor, i.e. for wiki pages or the work packages description. For example, you can now adjust the image size in the editor.

Additionally, it is now possible to add macros to insert project or work packages attributes to the wiki or work package description.

Attribute help texts for projects (premium feature)

We have now also expanded the attribute help texts for projects. You can define help text for all project attributes, such as status or accountable or any custom field for projects. A small question mark icon will appear behind the attribute in order to make the entry of this information easier and eliminate errors.

Copy boards and project dashboards

Boards and project dashboards can now also be copied when copying a project. This enables you to set up a default project and copy it to set up a new project.

Help and feedback

If you did not find what you were looking for

Search in docs

If you need help from the community or want to support others

Post on OpenProject forum

If you are eligible for professional support and have more questions

Request support

If you find an easily fixable error or need for improvement in the documentation

Edit this page

If you would like to suggest bigger updates or improvements to this documentation

Create an issue

If you want to contribute to translate this documentation to another language

Translate on crowdin

If there’s something you don’t like or understand about this feature

Create an issue

If you want to propose a new feature that OpenProject does not offer yet

Submit feature proposal

To further help OpenProject to shape and test new features

Join beta testing

To view OpenProject premium features and pricing

View pricing page

If you want to try all premium features in the OpenProject Cloud Edition 14 days for free

Free trial OpenProject Cloud Edition

If you want to try all premium features in your on premise Community installation 14 days for free

Free trial OpenProject Enterprise Edition (on premise)

Docker-based installation

If you are using docker-compose, then the data volumes are managed by Docker and you should have a look at the official Docker documentation for instructions on how to backup.

If you are using the all-in-one container, then you can simply backup any local volumes that you chose to bind-mount with the option when launching the container. For instance if you launched the container with:

Then you would need to backup the folder (for instance to S3 or FTP server).

Dumping the database

When using docker-compose you can simply dump the database from the database container.

This assumes that the database container is called . Find out the actual name on your host using .

All-in-one container

If you need a regular dump of the database you can get one using like this:

Where is the name of your OpenProject container. If you don’t know it you can find it using .

Upgrade notes for OpenProject 7.x to 8.x

These following points are some known issues around the update to 8.0. It does not contain the entire list of changes. To see all changes, please browse the release notes.

Upgrades in NPM may result in package inconsistencies

As has been reported from the community, there appear to be issues with NPM leftover packages upgrading to OpenProject 8.0.0. This is due to the packages applying a delta between your installed version and the to-be-installed 8.0. package. In some cases such as SLES12 and Centos 7, the folder is not fully correctly replaced. This appears to hint at an issue with yum, the package manager behind both.

To ensure the package’s node_modules folder matches your local version, we recommend you simply remove entirely before installing the package

Migration from Textile to Markdown

OpenProject 8.0. has removed Textile, all previous content is migrated to GFM Markdown using pandoc. This will happen automatically during the migration run. A recent pandoc version will be downloaded by OpenProject.

Offline/air-gapped installation

It’s possible to run the docker image on an a system with no internet access using and . The installation works the same as described above. The only difference is that you don’t download the image the usual way.

1) Save the image

On a system that has access to the internet run the following.

This creates a compressed archive containing the latest OpenProject docker image. The file will have a size of around 700mb.

2) Transfer the file onto the system

Copy the file onto the target system by any means that works. This could be sftp, scp or even via a USB stick in case of a truly air-gapped system.

3) Load the image

Once the file is on the system you can load it like this:

This extracts the archive and loads the contained image layers into docker. The .tar file can be deleted after this.

4) Proceed with the installation

After this both installation and later upgrades work just as usual. You only replaced or the normal, implicit download of the image with the steps described here.

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *

Adblock
detector