Repository files navigation

Application for managing your account, instances, teams and blueprints within the Zesty.io CMS

Start by creating a free instance

You have found the code base which powers the Zesty.io account management experience. While this code base can be run locally it is only recommended to do so for developing. If you would like to learn more about Zesty.io visit ourdocumentation at zesty.org

Browser Support

• Chrome / Firefox / Edge / Safari (latest)
• IE11
  • https://github.com/philipwalton/flexbugs#flexbug-4

We are working towards thePRPL pattern for delivering a PWA as described byAddy Osmani on developers.google.com

Currently we bundle our "sub-apps" individually but include them all on initial load. Eventually we want these bundles to be loaded on demand when their views are visited and the code becomes necessary.

We useRedux for managing our state and follow a single app store pattern. All persistent application state is maintained in a single global store.

TheZesty.io design system is our central location for components and patterns which are shared across our various external and internal applications. Our design system follows theatomic design pattern popularized by Brad Frost.

Can be installed vianpm install @zesty-io/core into any application. This is under active development and will have major breaking changes until we land 1.0.NOT PRODUCTION READY

When ever possible we want to communicate useful information to end users when errors occur. Using ourglobal notification component we are able to provide a consistent and learned behavior for our users to understand when actions are successful or fail. As well as hopefully being able to provide a solution to failures.

Being aware of errors your users experience is an important part of iterating and improving upon an application. We useSentry for error aggregation in order to capture, debug and report on code quality.

npm run start

This will install all necessary dependencies and do a development build which will begin watching your files and rebuild when changes occur. You will need the complete stack running in order to load the account-ui.

To setup your local environment for tests run:

npm run test:setup

This pulls the secrets file down and adds a DNS entry in your/etc/hosts file for routing requests toaccounts.dev.zesty.io back to localhost to prevent running into CORS issues.

Note

If you find yourself actually needing to login to the remote dev environment then don't forget to comment out the following line in your/etc/hosts file that was added by the above script:

127.0.0.1 accounts.dev.zesty.io

Otherwise you'll be routed to localhost.

Then you can either:

1 - Run your tests in headless mode:

npm run test

2 - Selectively run your tests in the Cypress UI:

npm run test:open

This application is configured to run and deploy against our internal stack and process. As such we do not provide a way to run onlocalhost.

When deploying it is important to use thenpm run build-production command as this will cause a productionwebpack build which adds large optimizations to the bundle size and runtime code.

Copyright (C)Zesty.io Inc.