Doppler Unlayer Editor

This project is a POC about adapting Unlayer to edit Doppler templates.

Development

It is based on Create React App. You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Available Scripts

In the project directory, you can run:

`yarn start`

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

Note: For local run, make sure to set Unlayer Account data (PROJECT_ID, USERID, USER_SIGNATURE) in .env.development.local

`yarn test`

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

`yarn coverage:local`

Launches the test runner with report coverage in the interactive watch mode.

You can view the generated report by opening ./coverage/lcov-report/index.html file in any web browser.

`yarn verify-format`

Runs some code formatting validations:

`yarn build`

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

`yarn eject` (Create React App)

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

CI / CD

We are using Jenkins as our CI/CD engine. .doppler-jenkins-ci.groovy is a declarative self documented file that you can use as the detailed documentation about the build and deployment process.

The build details can be found in Dockerfile.

The details about how do we deal with semantic version and what are we uploading to the CDN are in [./build-n-publish.sh] and cdn-helpers/prepare.sh

This approach is very similar to what we are doing with Docker images. See a description in doppler-forms project.

Basically it works in the following way:

Pull requests

When a pull request is created or updated, a build process is run and, if it is successful, the files are uploaded to our CDN.

For example, for the PR #7 it uploaded:

https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-pr-7.json - With the references to the actual files (.js and .css). This file is updated when a new commit is added to the PR.
https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-pr-7-111c328b28a250b7117c5c04f28a31748414c712.json - The canonical version, with the same content than the previous file, this file is not mutable.
https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-pr-7.txt with the detail about the last canonical version related to PR 7.

`main` branch

When a commit is merged in the main branch a build process is run and, if it is successful, the files are uploaded to our CDN.

For example, currently these files are uploaded:

https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-main.json - With the references to the actual files (.js and .css). This file is updated when a new commit is pushed to the main branch.
https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-main-fdf99016cce59a466dcecd17429af0b2d0f7b9f2.json - The canonical version, with the same content than the previous file, this file is not mutable.
https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-main.txt with the detail about the last canonical version related to the main version.

`INT` branch

When a commit is merged in the INT branch a build process is run and, if it is successful, the files are uploaded to our CDN.

For example, currently these files are uploaded:

https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-INT.json - With the references to the actual files (.js and .css). This file is updated when a new commit is pushed to the INT branch.
https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-INT-fdf99016cce59a466dcecd17429af0b2d0f7b9f2.json - The canonical version, with the same content than the previous file, this file is not mutable.
https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-INT.txt with the detail about the last canonical version related to the INT version.

Version tags

When a tag is generated, a build process is run and, if it is successful, the files are uploaded to our CDN.

For example, currently for tag v1.0.0:

https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-v1.json - With the references to the actual files (.js and .css). This file is updated when a new tag with the format v1.#.# is generated.
https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-v1.txt with the detail about the last canonical version related to a v1.#.# version.
https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-v1.0.json - With the references to the actual files (.js and .css). This file is updated when a new tag with the format v1.0.# is generated.
https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-v1.0.txt with the detail about the last canonical version related to a v1.0.# version.
https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-v1.0.0.json - With the references to the actual files (.js and .css). This file is updated when a new tag with the format v1.0.0 is generated.
https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-v1.0.0.txt with the detail about the last canonical version related to a v1.0.0 version.
https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-v1.0.0-fdf99016cce59a466dcecd17429af0b2d0f7b9f2.json - The canonical version, with the same content than the previous files, this file is not mutable.

Static files

All the static files referenced in the asset-manifest-* files are stored in http://cdn.fromdoppler.com/unlayer-editor/static.

Embed the editor

To use the editor, you should include a reference to the desired asset-manifest-* file. For example:

asset-manifest-v1.json, you will have the last final versions until a breaking change increment the mayor version to v2.
asset-manifest-main.json, you will have the last code merged the main branch.
asset-manifest-INT.json, you will have the last code pushed to the INT branch.

Currently in Doppler we are always using the v1:

<html lang="en">
  <head>
    <!-- . . . -->
    <script src="https://cdn.fromdoppler.com/mfe-loader/loader-v2.0.0.js"></script>
  </head>

  <body>
    <!-- . . . -->
    <script type="text/javascript">
      assetServices.load({
        manifestURL:
          'https://cdn.fromdoppler.com/unlayer-editor/asset-manifest-v1.json',
        sources: [],
      });
    </script>
    <!-- . . . -->
  </body>
</html>

File storage

AWS S3 storage configuration

Unlayer have file storage support built-in with Amazon S3 that can be configured without any coding. Follow these steps to set up your S3 file storage.

Create S3 Bucket: The first step is to create a bucket in your AWS S3 console. You need to uncheck "'Block all public access" for S3 storage.
Create IAM User: Go to your AWS IAM console and create a new user with Programmatic Access so you can get the access key id and secret access key.

Attach Policy and Permissions: Aattach a minimum set of permissions, use the following policy. Make sure to replace BUCKET-NAME, ID-COUNT, ID-USER with your actual bucket settings.

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "AllowFullAccessBucket",
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::ID-COUNT:user/ID-USER"
      },
      "Action": [
        "s3:GetBucketPublicAccessBlock",
        "s3:PutObject",
        "s3:GetObject",
        "s3:PutBucketPublicAccessBlock",
        "s3:GetBucketCORS",
        "s3:ListBucket",
        "s3:PutBucketCORS",
        "s3:GetBucketAcl",
        "s3:GetBucketLocation",
        "s3:PutObjectAcl",
        "s3:PutBucketTagging"
      ],
      "Resource": ["arn:aws:s3:::BUCKET-NAME/*", "arn:aws:s3:::BUCKET-NAME"]
    }
  ]
}

Enable CORS for your S3 Bucket: Your S3 Bucket must have CORS (cross-origin resource sharing) enabled. Follow these steps:
- Go to your S3 Bucket in AWS Console
- Click the Permissions tab
- Click the CORS Configuration button
- Add the following in the configuration editor
```
[
  {
    "AllowedHeaders": [],
    "AllowedMethods": ["PUT", "POST", "DELETE", "HEAD"],
    "AllowedOrigins": ["https://*.unlayer.com"],
    "ExposeHeaders": []
  }
]
```
Add Credentials in your Unlayer Project: Simply enter your information of S3 storage against your project. For this:
- Login to Unlayer dashboard
- Select your Project
- Click Settings in the navigation bar and select the Storage tab
- Click the Add Storage button
- Enter your Access Key Id, Secret Access Key, and Bucket
- Check Primary Storage at the end
Test your File Storage: Click the Test Storage button and see if all the items are working properly. If any of these are red, the storage will not work. In that case, please make sure all permissions are properly attached and the bucket exists in the correct region.

Unlayer project configuration: You must pass projectId when initializing the editor.

<script type="text/javascript">
  unlayer.init({
    id: 'editor',
    projectId: XXXX, // Add your projectId from Settings
  });
</script>

Real use case: When an image is uploaded by any user, it's image created inside the S3 bucket with a timestamp prefix to make it unique. If the image is loaded again, a new file will be created inside the s3 bucket no matter it is the same image.

Name		Name	Last commit message	Last commit date
Latest commit History 3,018 Commits
.vscode		.vscode
cdn-helpers		cdn-helpers
docs		docs
public		public
src		src
.babelrc		.babelrc
.dockerignore		.dockerignore
.editorconfig		.editorconfig
.env.development		.env.development
.env.production		.env.production
.eslintrc.json		.eslintrc.json
.estlintignore		.estlintignore
.gitattributes		.gitattributes
.gitignore		.gitignore
.gitlint		.gitlint
.prettierignore		.prettierignore
.prettierrc.json		.prettierrc.json
Dockerfile		Dockerfile
README.md		README.md
build-n-publish.sh		build-n-publish.sh
doppler-jenkins-ci.groovy		doppler-jenkins-ci.groovy
gitlint.sh		gitlint.sh
package.json		package.json
renovate.json		renovate.json
tsconfig.json		tsconfig.json
webpack-dev-server.config.js		webpack-dev-server.config.js
webpack.config.js		webpack.config.js
yarn.lock		yarn.lock

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Doppler Unlayer Editor

Development

Available Scripts

`yarn start`

`yarn test`

`yarn coverage:local`

`yarn verify-format`

`yarn build`

`yarn eject` (Create React App)

CI / CD

Pull requests

`main` branch

`INT` branch

Version tags

Static files

Embed the editor

File storage

AWS S3 storage configuration

About

Releases 1

Packages

Contributors 9

Languages

FromDoppler/unlayer-editor

Folders and files

Latest commit

History

Repository files navigation

Doppler Unlayer Editor

Development

Available Scripts

yarn start

yarn test

yarn coverage:local

yarn verify-format

yarn build

yarn eject (Create React App)

CI / CD

Pull requests

main branch

INT branch

Version tags

Static files

Embed the editor

File storage

AWS S3 storage configuration

About

Resources

Stars

Watchers

Forks

Releases 1

Packages 0

Contributors 9

Languages

`yarn start`

`yarn test`

`yarn coverage:local`

`yarn verify-format`

`yarn build`

`yarn eject` (Create React App)

`main` branch

`INT` branch

Packages