hyper63 / alternative-stack

A Remix Stack using hyper cloud as a services tier

hyper

Use Clean Cloud Architecture to Scale on your Terms

Docs · Issues · What's New

• Introduction
• Status
• Running Locally
• Documentation
• Contributions
• Developer Setup
• Thank you

Introduction

👋 Hey 👋

Welcome to the hyper Service Framework project ⚡️!

Hyper is a multi-cloud, multi-language, service framework that enables best-of-breed cloud service utilization, from any cloud provider. By providing a simple and extensible context-bound API for the Cloud, the hyper Service Framework decouples application services from the infrastructure that powers them, positioning application software for growth and long term stability.

As a result, the hyper Service Framework helps software organizations build "optimally-scaled" software and software teams.

Hyper organizations tame technical debt, by using Clean Cloud Architecture to sensibly scale their software and software teams, only when the complexity is needed, and not all up-front.

Status

• Development
• Alpha
• Beta
• v1.0

Running Locally

You can run a hyper server locally, with 5 locally running hyper services, using hyper-nano, a precompiled executable binary of the hyper service framework.

curl https://hyperland.s3.amazonaws.com/hyper -o hyper-nano
chmod +x hyper-nano
./hyper-nano

Alternatively, if you're using node, you can run npx hyper-nano

This command will run a hyper server on PORT 6363 and store data for each hyper service in a directory named __hyper__ placed in the cwd [Ctrl/Cmd] - C will stop the service.

This nano version of hyper implements the following ports and adapters:

• data (powered by In-Memory MongoDB)
• cache (powered by Sqlite)
• storage (powered by your local file system)
• search (powered by Sqlite and Minisearch)
• queue (powered by Sqlite and an in-memory queue)

Learn more about hyper-nano and read our blog post

Documentation

For more information about hyper63 go to our documentation site. https://docs.hyper.io if you are unable to find the information you are looking for, post a question in our slack

Contributions

See Contributing to hyper.

Developer Setup

Fork this repo and use gitpod!

Gitpod

Thank you

• OpenSource Community
• CharlestonJS Community
• JRS Coding School Team
• And everyone else that has helped this project become successful!

alternative-stack's Issues

feat: option to use Fly.io as deployment platform

See #7 for reasoning

feat: option to use Vercel as deployment platform

Thank you for helping to improve the Alternative Stack!

If you have a feature idea for hyper, drop on into our
Slack!

Is your feature request related to a problem?

Many user's are trying to avoid AWS or working with a Cloud provider. Part of hyper's mantra is to make working with Cloud services, easier. Many folks just need to deploy their application to a scalable platform, then consume their hyper services from there, not ever needing an AWS account. Vercel integration would be great for this.

Describe the solution you'd like

On stack initialization, allow the user to choose Vercel or AWS as their deployment target, and set up the project accordingly.

The stack should default to Vercel

Additional context

The stack should default to Vercel, since it requires the least amount of setup.

fix: ignore lockfiles

Have you experienced this bug with the latest version of the template?

yes

Steps to Reproduce

remix-run/remix#3110

We're running npm/yarn/pnpm install in our CLI (both when creating & on init), so this could cause unnecessary lockfiles if the user's package manager is different from the one we included the lockfile for.

Expected Behavior

Initialize the stack

Actual Behavior

Should implement something similar to remix-run/grunge-stack#53

Could not resolve test route

Have you experienced this bug with the latest version of the template?

Yes

Steps to Reproduce

1. npx create-remix --template hyper63/alternative-stack
2. npm run dev

Expected Behavior

Dev server able to start

Actual Behavior

npm run dev
...
Watching Remix app in development mode...
⚠️ Test routes enabled.
[WARN] Using experimental features. These features can change at any time.
{ ok: false, msg: "cache already exists", status: 409 }
CACHE:CREATE_STORE: {"date":"2022-09-02T16:40:30.819Z","ok":false,"status":409,"msg":"cache already exists"}
{ INFO: loaded databases: [notes-dev], DATE: 2022-09-02T16:40:30.832Z }
{ ok: false, msg: "database already exists", status: 409 }
DATA:CREATE_DB: {"date":"2022-09-02T16:40:30.837Z","ok":false,"status":409,"msg":"database already exists"}
[INFO] Created cache ⭐️ service in notes-dev domain ⚡️
[INFO] Created data 💿 service in notes-dev domain ⚡️

✘ [ERROR] Could not resolve ".//Users/maxim/src/cashflow-companion/test/test-routes/delete-user.ts"

    browser-route-module:/Users/maxim/src/cashflow-companion/test/test-routes/delete-user.ts?browser:1:24:
      1 │ ...ult } from ".//Users/maxim/src/cashflow-companion/test/test-rout...
        ╵               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Build failed with 1 error:
browser-route-module:/Users/maxim/src/cashflow-companion/test/test-routes/delete-user.ts?browser:1:24: ERROR: Could not resolve ".//Users/maxim/src/cashflow-companion/test/test-routes/delete-user.ts"
💿 Built in 564ms

The file is present and for some reason remix is not able to find it.