Giter Site home page Giter Site logo

collaborne-frontend-proxy's Introduction

collaborne-frontend-proxy Build Status Greenkeeper badge

This is a simple proxy for static websites hosted on S3, which is aware of a directory structure: instead of having one bucket for each application + version, it manages applications and versions as prefixes in S3, so application 'foo' with version '38271ad' would be searched for in the bucket under prefix foo/38271ad, and would be accessible under CFP-URL/app/foo/38271ad.

CFP supports marking a version as 'current', and it tracks whichever version was 'current' before as 'previous': CFP-URL/app/foo/current would open the current version, and CFP-URL/app/foo/previous would open the previous one. Additionally CFP tracks the latest created version as 'latest'.

CFP authorizes uses via GitHub: each user that is allowed to use the UI needs to be registered with their GitHub id in the users table. The applications themselves are not protected, so the links are shareable easily with designers and other stakeholders.

Running

This project assumes various environment variables to be set in order to work:

Variable Description
DATABASE_URL URL to a Postgres (9.1+) database with tables.sql loaded.
CFP_AWS_BUCKET Name of the bucket in S3
CFP_JWT_KEY Key for signing the JWTs, should be random enough.
AWS_ACCESS_KEY_ID AWS SDK Access Key Id
AWS_SECRET_ACCESS_KEY AWS SDK Secret Access Key
GH_CLIENT_ID Client ID for the GitHub integration
GH_CLIENT_SECRET Client secret for the GitHub integration
GH_WEBHOOK_SECRET Secret used for signing webhook events

The easiest way to get CFP running is to use Heroku with their Postgres add-on.

License

This software is licensed under the Apache 2 license, quoted below.

Copyright 2016-2017 Collaborne B.V. <http://github.com/Collaborne/>

Licensed under the Apache License, Version 2.0 (the "License"); you may not
use this file except in compliance with the License. You may obtain a copy of
the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations under
the License.

collaborne-frontend-proxy's People

Contributors

ankon avatar greenkeeper[bot] avatar

Watchers

 avatar  avatar  avatar  avatar

Forkers

cloudxtreme

collaborne-frontend-proxy's Issues

Implement support for deleting apps and versions

This would require a concept of 'permissions' and 'roles' for a user, and then we should be able to add a middleware to the API calls to check that req.user.permissions contains the required permissions for the functionality.

Add a 'latest' name

'latest' should always point to the last-created version, regardless of where 'current' points to.

An in-range update of aws-sdk is breaking the build 🚨

Version 2.247.1 of aws-sdk was just published.

Branch Build failing 🚨
Dependency aws-sdk
Current Version 2.246.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

aws-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes Release v2.247.1

See changelog for more information.

Commits

The new version differs by 1 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of aws-sdk is breaking the build 🚨

Version 2.262.1 of aws-sdk was just published.

Branch Build failing 🚨
Dependency [aws-sdk](https://github.com/aws/aws-sdk-js)
Current Version 2.261.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

aws-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes Release v2.262.1

See changelog for more information.

Commits

The new version differs by 1 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Allow overriding paths via configuration

CFP is a proxy, and it really doesn't care where things go to: in theory it could serve paths from different locations.

This fits nicely with a static web app: configuration information (for example in form of javascript/json files) would have to be loaded by the app, and if CFP could include overrides for paths it would be possible to point different applications to use different configurations.

This would basically require a new table:

CREATE TABLE overrides (app VARCHAR PRIMARY KEY, path VARCHAR NOT NULL, url VARCHAR NOT NULL)

An in-range update of aws-sdk is breaking the build 🚨

Version 2.108.0 of aws-sdk just got published.

Branch Build failing 🚨
Dependency aws-sdk
Current Version 2.107.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

aws-sdk is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes Release v2.108.0

See changelog for more information.

Commits

The new version differs by 1 commits.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of aws-sdk is breaking the build 🚨

The dependency aws-sdk was updated from 2.351.0 to 2.352.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

aws-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for Release v2.352.0

See changelog for more information.

Commits

The new version differs by 2 commits.

  • 72c0480 Updates SDK to v2.352.0
  • cbef864 Endpoint Discovery Feature (#2253)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of aws-sdk is breaking the build 🚨

Version 2.289.0 of aws-sdk was just published.

Branch Build failing 🚨
Dependency aws-sdk
Current Version 2.288.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

aws-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes Release v2.289.0

See changelog for more information.

Commits

The new version differs by 1 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of request is breaking the build 🚨

Version 2.88.0 of request was just published.

Branch Build failing 🚨
Dependency request
Current Version 2.87.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

request is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 13 commits.

  • 6420240 2.88.0
  • bd22e21 fix: massive dependency upgrade, fixes all production vulnerabilities
  • 925849a Merge pull request #2996 from kwonoj/fix-uuid
  • 7b68551 fix(uuid): import versioned uuid
  • 5797963 Merge pull request #2994 from dlecocq/oauth-sign-0.9.0
  • 628ff5e Update to oauth-sign 0.9.0
  • 10987ef Merge pull request #2993 from simov/fix-header-tests
  • cd848af These are not going to fail if there is a server listening on those ports
  • a92e138 #515, #2894 Strip port suffix from Host header if the protocol is known. (#2904)
  • 45ffc4b Improve AWS SigV4 support. (#2791)
  • a121270 Merge pull request #2977 from simov/update-cert
  • bd16414 Update test certificates
  • 536f0e7 2.87.1

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of bower is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 1.8.3 of bower was just published.

Branch Build failing 🚨
Dependency bower
Current Version 1.8.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

bower is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml
  • The engines config in 1 of your package.json files was updated to the new Node.js version

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of bower is breaking the build 🚨

Version 1.8.1 of bower just got published.

Branch Build failing 🚨
Dependency bower
Current Version 1.8.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As bower is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of aws-sdk is breaking the build 🚨

Version 2.18.0 of aws-sdk just got published.

Branch Build failing 🚨
Dependency aws-sdk
Current Version 2.17.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As aws-sdk is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Release Notes Release v2.18.0

See changelog for more information.

Commits

The new version differs by 1 commits .

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of pg is breaking the build 🚨

Version 7.3.0 of pg just got published.

Branch Build failing 🚨
Dependency pg
Current Version 7.2.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

pg is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 25 commits.

  • f66379f Bump version
  • dfc7214 Update changelog
  • f1336fc Change Makefile to use local eslint
  • ecab41c restore newline at end of file
  • 64eb77e new test for actual statement timeout
  • 175b688 remove pg-native from dependencies
  • 689bb25 fixes
  • 78fc903 remove .idea from gitignore
  • 8839d42 fixed test failure message
  • ad36063 support statement_timeout
  • 4936033 Check more default properties in configuration teset
  • d6e7dfe Replace poolSize by max in configuration test
  • 3b3e52c Prefer max over poolSize : max is the only property documented in node-pg-pool
  • 27492ef Remove properties no more used in node-pg-pool
  • c961888 Revert "Update Grammatical person"

There are 25 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of yargs is breaking the build 🚨

The devDependency yargs was updated from 13.2.2 to 13.2.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

yargs is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 14 commits.

  • a6e67f1 chore(release): 13.2.4
  • fc13476 chore: update standard-verison dependency
  • bf46813 fix(i18n): rename unclear 'implication failed' to 'missing dependent arguments' (#1317)
  • a3a5d05 docs: fix a broken link to MS Terminology Search (#1341)
  • b4f8018 build: add .versionrc that hides test/build
  • 0c39183 chore(release): 13.2.3
  • 08e0746 chore: update deps (#1340)
  • 843e939 docs: make --no- boolean prefix easier to find in the docs (#1338)
  • 84cac07 docs: restore removed changelog of v13.2.0 (#1337)
  • b20db65 fix(deps): upgrade cliui for compatibility with latest chalk. (#1330)
  • c294d1b test: accept differently formatted output (#1327)
  • ac3f10c chore: move .hbs templates into .js to facilitate webpacking (#1320)
  • 0295132 fix: address issues with dutch translation (#1316)
  • 9f2468e doc: clarify parserConfiguration object structure (#1309)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of aws-sdk is breaking the build 🚨

The dependency aws-sdk was updated from 2.350.0 to 2.351.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

aws-sdk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Release Notes for Release v2.351.0

See changelog for more information.

Commits

The new version differs by 3 commits.

  • 70cbaa7 Updates SDK to v2.351.0
  • 4073d3d Merge pull request #2342 from srchase/npmignore-additions
  • 13b0dd3 updated npmignore, fix for issue #2341

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.