Console, you can see the exact version that's being used.
-
-
-
-Network tab, to check if there is a request that throws errors.
-
-
-
-
-
--Skip this section if you already have Helm installed in your system. -
- -You can install Helm by following the official guide. -There are different ways to install Helm, depending on your infrastructure and operating -system. - - -### Add Penpot repository - -To add the Penpot Helm repository, run the following command: - -```bash -helm repo add penpot http://helm.penpot.app -``` - -This will add the Penpot repository to your Helm configuration, so you can install all -the Penpot charts stored there. - - -### Install Penpot Chart - -To install the chart with the release name `my-release`: - -```bash -helm install my-release penpot/penpot -``` - -You can customize the installation specify each parameter using the `--set key=value[,key=value]` -argument to helm install. For example, - -```bash -helm install my-release \ - --set global.postgresqlEnabled=true \ - --set global.redisEnabled=true \ - --set persistence.assets.enabled=true \ - penpot/penpot -``` - -Alternatively, a YAML file that specifies the values for the above parameters can be -provided while installing the chart. For example, - -```bash -helm install my-release -f values.yaml penpot/penpot -``` - - -### Configure Penpot with Helm Chart - -In the previous section we have shown how to configure penpot during installation by -using parameters or by using a yaml file. - -The default values are defined in the -`values.yml` -file itself, which you can use as a basis for creating your own settings. - -You can also consult the list of parameters on the -ArtifactHub page of the project. - - -### Upgrade Penpot - -When a new version of Penpot's chart is released, or when you want to change the -configuration of your release, you can use the helm upgrade command. - -```bash -helm upgrade my-release -f values.yaml penpot/penpot -``` - -An upgrade takes an existing release and upgrades it according to the information you -provide. Because Kubernetes charts can be large and complex, Helm tries to perform the -least invasive upgrade. It will only update things that have changed since the last -release. - -After each upgrade, a new *revision* will be generated. You can check the revision -history of a release with `helm history my-release` and go back to the previous revision -if something went wrong with `helm rollback my-release 1` (`1` is the revision number of -the previous release revision). - - -### Backup Penpot - -The Penpot's Helm Chart uses different Persistent Volumes to store all persistent data. -This allows you to delete and recreate the instance whenever you want without losing -information. - -You back up data from a Persistent Volume via snapshots, so you will want to ensure that -your container storage interface (CSI) supports volume snapshots. There are a couple of -different options for the CSI driver that you choose. All of the major cloud providers -have their respective CSI drivers. - -At last, there are two Persistent Volumes used: one for the Postgres database and another -one for the assets uploaded by your users (images and svg clips). There may be more -volumes if you enable other features, as explained in the file itself. - -You have to back up your custom settings too (the yaml file or the list of parameters you -are using during you setup). - - -## Unofficial self-host options - -There are some other options, **NOT SUPPORTED BY PENPOT**: - -* Install with Podman instead of Docker. -* Try the under development Penpot Desktop app. -* Try a simple Kubernetes Deployment option penpot-kubernetes. -* Or try a fully manual installation if you have a really specific use case.. For help, you can look at the [Architecture][2] section and the Docker configuration files. - -[1]: /technical-guide/configuration/ -[2]: /technical-guide/developer/architecture diff --git a/docs/technical-guide/getting-started/docker.md b/docs/technical-guide/getting-started/docker.md new file mode 100644 index 000000000..400714498 --- /dev/null +++ b/docs/technical-guide/getting-started/docker.md @@ -0,0 +1,239 @@ +--- +title: 1.3 Install with Docker +--- + +# Install with Docker + +This section details everything you need to know to get Penpot up and running in +production environments using Docker. For this, we provide a series of *Dockerfiles* and a +*docker-compose* file that orchestrate all. + +## Install Docker + ++Skip this section if you already have docker installed, up and running. +
+ +Currently, Docker comes into two different flavours: + +### Docker Desktop + +This is the only option to have Docker in a Windows or MacOS. Recently it's also available +for Linux, in the most popular distributions (Debian, Ubuntu and Fedora). + +You can install it following the official guide. + +Docker Desktop has a graphical control panel (GUI) to manage the service and view the +containers, images and volumes. But you need the command line (Terminal in Linux and Mac, or +PowerShell in Windows) to build and run the containers, and execute other operations. + +It already includes **docker compose** utility, needed by Penpot. + +### Docker Engine + +This is the classic and default Docker setup for Linux machines, and the only option for a +Linux VPS without graphical interface. + +You can install it following the official guide. + +And you also need the [docker +compose](https://docs.docker.com/compose/cli-command/#installing-compose-v2) (V2) +plugin. You can use the old **docker-compose** tool, but all the documentation supposes +you are using the V2. + +You can easily check which version of **docker compose** you have. If you can execute +docker compose command, then you have V2. If you need to write docker-compose (with a
+-) for it to work, you have the old version.
+
+## Start Penpot
+
+As a first step you will need to obtain the docker-compose.yaml file. You can download it
+from the Penpot repository.
+
+```bash
+wget https://raw.githubusercontent.com/penpot/penpot/main/docker/images/docker-compose.yaml
+```
+or
+```bash
+curl -o docker-compose.yaml https://raw.githubusercontent.com/penpot/penpot/main/docker/images/docker-compose.yaml
+```
+
+Then simply launch composer:
+
+```bash
+docker compose -p penpot -f docker-compose.yaml up -d
+```
+
+At the end it will start listening on http://localhost:9001
+
++ If you don't change anything, by default this will use the latest image published in dockerhub. +
+ +If you want to have more control over the version (which is recommended), you can use the PENPOT_VERSION envvar in the common ways: +- setting the value in the .env file +- or passing the envvar in the command line + +```bash +PENPOT_VERSION=2.4.3 docker compose -p penpot -f docker-compose.yaml up -d +``` + +## Stop Penpot + +If you want to stop running Penpot, just type + +```bash +docker compose -p penpot -f docker-compose.yaml down +``` + +## Configure Penpot with Docker + +The configuration is defined using flags and environment variables in thedocker-compose.yaml
+file. The default downloaded file comes with the essential flags and variables already set,
+and other ones commented out with some explanations.
+
+You can find all configuration options in the [Configuration][1] section.
+
+## Using the CLI for administrative tasks
+
+Penpot provides a script (`manage.py`) with some administrative tasks to perform in the server.
+
+**NOTE**: this script will only work with the enable-prepl-server
+flag set in the docker-compose.yaml file. For older versions of docker-compose.yaml file,
+this flag is set in the backend service.
+
+For instance, if the registration is disabled, the only way to create a new user is with this script:
+
+```bash
+docker exec -ti penpot-penpot-backend-1 python3 manage.py create-profile
+```
+
+**NOTE:** the exact container name depends on your docker version and platform.
+For example it could be penpot-penpot-backend-1 or penpot_penpot-backend-1.
+You can check the correct name executing docker ps.
+
+## Update Penpot
+
+To get the latest version of Penpot in your local installation, you just need to
+execute:
+
+```bash
+docker compose -f docker-compose.yaml pull
+```
+
+This will fetch the latest images. When you do docker compose up again, the containers will be recreated with the latest version.
+
++ It is strongly recommended to update the Penpot version in small increments, rather than updating between two distant versions. +
+ +**Important: Upgrade from version 1.x to 2.0** + +The migration to version 2.0, due to the incorporation of the new v2 components, includes +an additional process that runs automatically as soon as the application starts. If your +on-premises Penpot instance contains a significant amount of data (such as hundreds of +penpot files, especially those utilizing SVG components and assets extensively), this +process may take a few minutes. + +In some cases, such as when the script encounters an error, it may be convenient to run +the process manually. To do this, you can disable the automatic migration process using +thedisable-v2-migration flag in PENPOT_FLAGS environment variable. You can then execute the
+migration process manually with the following command:
+
+```bash
+docker exec -ti +Skip this section if you already have an Elestio account. +
+ +To create your Elestio account click here. You can choose to deploy on any one of five leading cloud +providers or on-premise. + +## Deploy Penpot using Elestio + +Now you can Create your service in “Services”: +1. Look for Penpot. +2. Select a Service Cloud Provider. +3. Select Service Cloud Region. +4. Select Service Plan (for a team of 20 you should be fine with 2GB RAM). +5. Select Elestio Service Support. +6. Provide Service Name (this will show in the URL of your instance) & Admin email (used + to create the admin account). +7. Select Advanced Configuration options (you can also do this later). +8. Hit “Create Service” on the bottom right. + +It will take a couple of minutes to get the instance launched. When the status turns to +“Service is running” you are ready to get started. + +By clicking on the Service you go to all the details and configuration options. + +In Network/CNAME you can find the URL of your instance. Copy and paste this into a browser +and start using Penpot. + +## Configure Penpot with Elestio + +If you want to make changes to your Penpot setup click on the “Update config” button in +Software. Here you can see the “Docker compose” used to create the instance. In “ENV” top +middle left you can make configuration changes that will be reflected in the Docker +compose. + +In this file, a “#” at the start of the line means it is text and not considered part of +the configuration. This means you will need to delete it to get some of the configuration +options to work. Once you made all your changes hit “Update & restart”. After a couple of +minutes, your changes will be active. + +You can find all configuration options in the [Configuration][1] section. + +Get in contact with us through support@penpot.app +if you have any questions or need help. + +## Update Penpot + +Elestio will update your instance automatically to the latest release unless you don't +want this. In that case you need to “Disable auto updates” in Software auto updates. + +[1]: /technical-guide/configuration/ diff --git a/docs/technical-guide/getting-started/index.md b/docs/technical-guide/getting-started/index.md new file mode 100644 index 000000000..bdf6812cb --- /dev/null +++ b/docs/technical-guide/getting-started/index.md @@ -0,0 +1,31 @@ +--- +title: 1. Self-hosting Guide +--- + +# Self-hosting Guide + +This guide explains how to get your own Penpot instance, running on a machine you control, +to test it, use it by you or your team, or even customize and extend it any way you like. + +If you need more context you can look at the post +about self-hosting in Penpot community. + +**There is absolutely no difference between our SaaS offer for Penpot and your +self-hosted Penpot platform!** + +There are three main options for creating a Penpot instance: + +1. Using the platform of our partner Elestio. +2. Using Docker tool. +3. Using Kubernetes. + ++The recommended way is to use Elestio, since it's simpler, fully automatic and still greatly flexible. +Use Docker if you already know the tool, if need full control of the process or have extra requirements +and do not want to depend on any external provider, or need to do any special customization. +
+ +Or you can try other options, +offered by Penpot community. diff --git a/docs/technical-guide/getting-started/kubernetes.md b/docs/technical-guide/getting-started/kubernetes.md new file mode 100644 index 000000000..ccfe79a5c --- /dev/null +++ b/docs/technical-guide/getting-started/kubernetes.md @@ -0,0 +1,136 @@ +--- +title: 1.4 Install with Kubernetes +--- + +# Install with Kubernetes + +This section details everything you need to know to get Penpot up and running in +production environments using a Kubernetes cluster of your choice. To do this, we have +created a Helm repository with everything +you need. + +Therefore, your prerequisite will be to have a Kubernetes cluster on which we can install +Helm. + +## What is Helm + +*Helm* is the package manager for Kubernetes. A *Chart* is a Helm package. It contains +all of the resource definitions necessary to run an application, tool, or service inside +of a Kubernetes cluster. Think of it like the Kubernetes equivalent of a Homebrew +formula, an Apt dpkg, or a Yum RPM file. + +A Repository is the place where charts can be collected and shared. It's like Perl's CPAN +archive or the Fedora Package Database, but for Kubernetes packages. + +A Release is an instance of a chart running in a Kubernetes cluster. One chart can often +be installed many times into the same cluster. And each time it is installed, a new +release is created. Consider a MySQL chart. If you want two databases running in your +cluster, you can install that chart twice. Each one will have its own release, which will +in turn have its own release name. + +With these concepts in mind, we can now explain Helm like this: + +> Helm installs charts into Kubernetes clusters, creating a new release for each +> installation. To find new charts, you can search Helm chart repositories. + + +## Install Helm + ++Skip this section if you already have Helm installed in your system. +
+ +You can install Helm by following the official guide. +There are different ways to install Helm, depending on your infrastructure and operating +system. + + +## Add Penpot repository + +To add the Penpot Helm repository, run the following command: + +```bash +helm repo add penpot http://helm.penpot.app +``` + +This will add the Penpot repository to your Helm configuration, so you can install all +the Penpot charts stored there. + + +## Install Penpot Chart + +To install the chart with the release name `my-release`: + +```bash +helm install my-release penpot/penpot +``` + +You can customize the installation by specifying each parameter using the `--set key=value[,key=value]` +argument to helm install. For example, + +```bash +helm install my-release \ + --set global.postgresqlEnabled=true \ + --set global.redisEnabled=true \ + --set persistence.assets.enabled=true \ + penpot/penpot +``` + +Alternatively, a YAML file that specifies the values for the above parameters can be +provided while installing the chart. For example, + +```bash +helm install my-release -f values.yaml penpot/penpot +``` + + +## Configure Penpot with Helm Chart + +In the previous section we have shown how to configure penpot during installation by +using parameters or by using a yaml file. + +The default values are defined in the +`values.yml` +file itself, which you can use as a basis for creating your own settings. + +You can also consult the list of parameters on the +ArtifactHub page of the project. + + +## Upgrade Penpot + +When a new version of Penpot's chart is released, or when you want to change the +configuration of your release, you can use the helm upgrade command. + +```bash +helm upgrade my-release -f values.yaml penpot/penpot +``` + +An upgrade takes an existing release and upgrades it according to the information you +provide. Because Kubernetes charts can be large and complex, Helm tries to perform the +least invasive upgrade. It will only update things that have changed since the last +release. + +After each upgrade, a new *revision* will be generated. You can check the revision +history of a release with `helm history my-release` and go back to the previous revision +if something went wrong with `helm rollback my-release 1` (`1` is the revision number of +the previous release revision). + + +## Backup Penpot + +The Penpot's Helm Chart uses different Persistent Volumes to store all persistent data. +This allows you to delete and recreate the instance whenever you want without losing +information. + +You back up data from a Persistent Volume via snapshots, so you will want to ensure that +your container storage interface (CSI) supports volume snapshots. There are a couple of +different options for the CSI driver that you choose. All of the major cloud providers +have their respective CSI drivers. + +At last, there are two Persistent Volumes used: one for the Postgres database and another +one for the assets uploaded by your users (images and svg clips). There may be more +volumes if you enable other features, as explained in the file itself. + +You have to back up your custom settings too (the yaml file or the list of parameters you +are using during you setup). diff --git a/docs/technical-guide/getting-started/recommended-settings.md b/docs/technical-guide/getting-started/recommended-settings.md new file mode 100644 index 000000000..7544ecc41 --- /dev/null +++ b/docs/technical-guide/getting-started/recommended-settings.md @@ -0,0 +1,13 @@ +--- +title: 1.1 Recommended Settings +--- + +# Recommended settings + +To self-host Penpot, you’ll need a server with the following specifications: + +* **CPU:** 1-2 CPUs +* **RAM:** 4 GiB of RAM +* **Disk Space:** Disk requirements depend on your usage. Disk usage primarily involves the database and any files uploaded by users. + +This setup should be sufficient for a smooth experience with typical usage (your mileage may vary). diff --git a/docs/technical-guide/getting-started/unofficial-options.md b/docs/technical-guide/getting-started/unofficial-options.md new file mode 100644 index 000000000..fea02fc83 --- /dev/null +++ b/docs/technical-guide/getting-started/unofficial-options.md @@ -0,0 +1,14 @@ +--- +title: 1.5 Unofficial self-host options +--- + +# Unofficial self-host options + +There are some other options, **NOT SUPPORTED BY PENPOT**: + +* Install with Podman instead of Docker. +* Try the under development Penpot Desktop app. +* Try a simple Kubernetes Deployment option penpot-kubernetes. +* Or try a fully manual installation if you have a really specific use case.. For help, you can look at the [Architecture][1] section and the Docker configuration files. + +[1]: /technical-guide/developer/architecture diff --git a/docs/technical-guide/index.md b/docs/technical-guide/index.md index 5197ea1b3..8f0b2783a 100644 --- a/docs/technical-guide/index.md +++ b/docs/technical-guide/index.md @@ -37,6 +37,11 @@ Also, if you are a developer, you can get into the code, to explore it, learn ho or extend it and contribute with new functionality. For this, we have a different Docker installation. In the [Developer Guide][6] you can find how to setup a development environment and many other dev-oriented documentation. +## Troubleshooting Penpot + +The [Troubleshooting][8] section guides you through the different logs in Penpot so you can easily identify +any issue that may arise as well as report it comprehensively. + [1]: /technical-guide/getting-started/#install-with-elestio [2]: /technical-guide/getting-started/#install-with-docker [3]: /technical-guide/configuration/ @@ -44,3 +49,4 @@ In the [Developer Guide][6] you can find how to setup a development environment [5]: /technical-guide/integration/ [6]: /technical-guide/developer/ [7]: /technical-guide/getting-started/#install-with-kubernetes +[8]: /technical-guide/troubleshooting/ diff --git a/docs/technical-guide/troubleshooting.md b/docs/technical-guide/troubleshooting.md new file mode 100644 index 000000000..56274258b --- /dev/null +++ b/docs/technical-guide/troubleshooting.md @@ -0,0 +1,62 @@ +--- +title: 5. Troubleshooting Penpot +--- + +# Troubleshooting Penpot + +Knowing how to do Penpot troubleshooting can be very useful; on the one hand, it helps to create issues easier to resolve, +since they include relevant information from the beginning which also makes them get solved faster; +on the other hand, many times troubleshooting gives the necessary information to resolve a problem autonomously, +without even creating an issue. + +Troubleshooting requires patience and practice; you have to read the stacktrace carefully, even if it looks like a mess at first. +It takes some practice to learn how to read the traces properly and extract important information. + +So, if your Penpot installation is not working as intended, there are several places to look up searching for hints. + +## Browser logs + +Regardless of the type of installation you have performed, you can find useful information about Penpot in your browser. + +First, use the devtools to ensure which version and flags you're using. Go to your Penpot instance in the browser and press F12; +you'll see the devtools. In theConsole, you can see the exact version that's being used.
+
+
+
+Other interesting tab in the devtools is the Network tab, to check if there is a request that throws errors.
+
+
+
+## Penpot report
+
+When Penpot crashes, it provides a report with very useful information. Don't miss it!
+
+
+
+## Docker logs
+
+If you are using the Docker installation, this is an easy way to take a look at the logs.
+
+Check if all containers are up and running:
+
+```bash
+docker compose -p penpot -f docker-compose.yaml ps
+```
+
+Check logs of all Penpot:
+
+```bash
+docker compose -p penpot -f docker-compose.yaml logs -f
+```
+
+If there is too much information and you'd like to check just one service at a time:
+
+```bash
+docker compose -p penpot -f docker-compose.yaml logs penpot-frontend -f
+```
+
+You can always check the logs form a specific container:
+
+```bash
+docker logs -f penpot-penpot-postgres-1
+```
diff --git a/frontend/src/app/main/data/workspace/libraries.cljs b/frontend/src/app/main/data/workspace/libraries.cljs
index 50c34adbb..dadb2af94 100644
--- a/frontend/src/app/main/data/workspace/libraries.cljs
+++ b/frontend/src/app/main/data/workspace/libraries.cljs
@@ -1189,20 +1189,19 @@
(ctf/used-assets-changed-since file-data library sync-date))))))
(defn notify-sync-file
+ ;; file-id is the id of the modified library
[file-id]
(dm/assert! (uuid? file-id))
(ptk/reify ::notify-sync-file
ptk/WatchEvent
(watch [_ state _]
- (let [file (dsh/lookup-file state file-id)
-
+ (let [file (dsh/lookup-file state (:current-file-id state))
file-data (get file :data)
ignore-until (get file :ignore-sync-until)
libraries-need-sync
(filter #(seq (assets-need-sync % file-data ignore-until))
(vals (get state :files)))
-
do-more-info
#(modal/show! :libraries-dialog {:starting-tab "updates" :file-id file-id})
diff --git a/frontend/src/app/main/data/workspace/notifications.cljs b/frontend/src/app/main/data/workspace/notifications.cljs
index f5e85bce2..e62985f70 100644
--- a/frontend/src/app/main/data/workspace/notifications.cljs
+++ b/frontend/src/app/main/data/workspace/notifications.cljs
@@ -317,6 +317,6 @@
(ptk/reify ::handle-library-change
ptk/WatchEvent
(watch [_ state _]
- (when (contains? (:libraries state) file-id)
+ (when (contains? (:files state) file-id)
(rx/of (dwl/ext-library-changed file-id modified-at revn changes)
(dwl/notify-sync-file file-id))))))