All Projects → quirrel-dev → quirrel.dev

quirrel-dev / quirrel.dev

Licence: other
Quirrel Landing Page & Console

Programming Languages

typescript
32286 projects
javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to quirrel.dev

owl
A high-performance, Redis-backed job queueing library originally built for Quirrel. Has an in-memory mode for development use cases.
Stars: ✭ 83 (+102.44%)
Mutual labels:  quirrel
nasulog
ポエム投稿サービス
Stars: ✭ 24 (-41.46%)
Mutual labels:  heroku
yt-heroku-demo
Code and instructions used in my YouTube video on how to deploy Spring Boot applications on Heroku
Stars: ✭ 21 (-48.78%)
Mutual labels:  heroku
create-mern-ts-app
Create a Mongo-Express-React-Node Application written in TypeScript out of the box.
Stars: ✭ 30 (-26.83%)
Mutual labels:  heroku
heroku-integrated-firefox-geckodriver
Buildpack enables your client code to access Firefox along with Geckodriver in a Heroku slug.
Stars: ✭ 40 (-2.44%)
Mutual labels:  heroku
salesforce-iam-flows
Node.js application that implements some of the most common SAML and OAuth flows in Salesforce.
Stars: ✭ 31 (-24.39%)
Mutual labels:  heroku
Flask Boilerplate
Simple flask boilerplate with Postgres, Docker, and Heroku/Zeit now
Stars: ✭ 251 (+512.2%)
Mutual labels:  heroku
trashed
Trashed is an organizational tool designed to help users keep their communities clean.
Stars: ✭ 13 (-68.29%)
Mutual labels:  heroku
haikunatorphp
Generate Heroku-like random names to use in your php applications.
Stars: ✭ 99 (+141.46%)
Mutual labels:  heroku
parsesig
A Telegram bot that forwards messages from one private/public channel to another after formatting
Stars: ✭ 40 (-2.44%)
Mutual labels:  heroku
node-postgres
This application demonstrates database operations using PostgreSQL as a database, Heroku as platform, Node.js as language and Angularjs as javascript based MVC.
Stars: ✭ 18 (-56.1%)
Mutual labels:  heroku
arugo
Virtual rating system for codeforces using codeforces API.
Stars: ✭ 30 (-26.83%)
Mutual labels:  heroku
laravel5-heroku
Laravel 5 with best practices for deployment on Heroku - created by
Stars: ✭ 18 (-56.1%)
Mutual labels:  heroku
secure-e2ee
Secure end-to-end-encryption for Node.js.
Stars: ✭ 24 (-41.46%)
Mutual labels:  quirrel
heroku-stack-container-repo
After deploying this repo your Heroku app will have stack as container. After that you just have to deploy your own original app.
Stars: ✭ 43 (+4.88%)
Mutual labels:  heroku
Heroku ebooks
A script to generate Markov chains and to post to an _ebooks account on Twitter using Heroku
Stars: ✭ 251 (+512.2%)
Mutual labels:  heroku
django-s3file
A lightweight file upload input for Django and Amazon S3
Stars: ✭ 66 (+60.98%)
Mutual labels:  heroku
NadekoBot
This is fork of the original NadekoBot, the general purpose of this fork is to make it work on Heroku cloud. Microsoft Sql Server and PostgreSQL edition.
Stars: ✭ 17 (-58.54%)
Mutual labels:  heroku
Deployment to heroku django
This is just a way of deploying to heroku with a django framework application.I hope i would be of help.
Stars: ✭ 30 (-26.83%)
Mutual labels:  heroku
htui
Heroku Terminal User Interface
Stars: ✭ 109 (+165.85%)
Mutual labels:  heroku

Blitz.js

All Contributors

This is a Blitz.js app.

name

Getting Started

Run your app in the development mode.

blitz dev

Open http://localhost:3000 with your browser to see the result.

Environment Variables

Ensure the .env.local file has required environment variables:

DATABASE_URL=postgresql://<YOUR_DB_USERNAME>@localhost:5432/console

Ensure the .env.test.local file has required environment variables:

DATABASE_URL=postgresql://<YOUR_DB_USERNAME>@localhost:5432/console_test

Tests

Runs your tests using Jest.

blitz test
or
yarn test

Blitz comes with a test setup using Jest and react-testing-library.

Commands

Blitz comes with a powerful CLI that is designed to make development easy and fast. You can install it with npm i -g blitz

  blitz [COMMAND]

  build     Create a production build
  console   Run the Blitz console REPL
  db        Run database commands
  generate  Generate new files for your Blitz project
  help      display help for blitz
  start     Start a development server
  test      Run project tests

You can read more about it on the CLI Overview documentation.

What's included?

Here is the structure of your app.

console
├── app
│   |── auth
│   │   ├── components
│   │   │   └── LoginForm.tsx
│   │   ├── mutations
│   │   │   ├── login.ts
│   │   │   ├── logout.ts
│   │   │   └── signup.ts
│   │   └── pages
│   │       ├── login.tsx
│   │       └── signup.tsx
│   ├── auth-utils.ts
│   ├── validations.ts
│   ├── components
│   │   ├── Form.tsx
│   │   └── LabeledTextField.tsx
│   ├── hooks
│   │   └── useCurrentUser.ts
│   ├── layouts
│   │   └── Layout.tsx
│   │── pages
│   │   ├── _app.tsx
│   │   ├── _document.tsx
│   │   ├── 404.tsx
│   │   ├── index.tsx
│   │   └── index.test.tsx
│   └── users
│   │   └── queries
│   │       └── getCurrentUser.ts
├── db
│   ├── migrations
│   ├── index.ts
│   └── schema.prisma
├── integrations
├── node_modules
├── public
│   ├── favicon.ico
│   └── logo.png
├── test
│   ├── __mocks__
│   │       └── fileMock.js
│   ├── setup.ts
│   └── utils.tsx
├── utils
├── .env
├── .eslintrc.js
├── .gitignore
├── .npmrc
├── .prettierignore
├── babel.config.js
├── blitz.config.js
├── jest.config.js
├── package.json
├── README.md
├── tsconfig.json
└── yarn.lock

These files are:

  • The app/ directory is a container for most of your project. This is where you’ll put any pages or API routes.

  • db/ is where your database configuration goes. If you’re writing models or checking migrations, this is where to go.

  • node_modules/ is where your “dependencies” are stored. This directory is updated by your package manager, so you don’t have to worry too much about it.

  • public/ is a directory where you will put any static assets. If you have images, files, or videos which you want to use in your app, this is where to put them.

  • test/ is a directory where you can put your unit and integration tests.

  • utils/ is a good place to put any shared utility files which you might use across different sections of your app.

  • .babelrc.js, .env, etc. ("dotfiles") are configuration files for various bits of JavaScript tooling.

  • blitz.config.js is for advanced custom configuration of Blitz. It extends next.config.js.

  • jest.config.js contains config for Jest tests. You can customize it if needed.

  • package.json contains information about your dependencies and devDependencies. If you’re using a tool like npm or yarn, you won’t have to worry about this much.

  • tsconfig.json is our recommended setup for TypeScript.

You can read more about it in the File Structure section of the documentation.

Learn more

Read the Blitz.js Documentation to learn more.

The Blitz.js Manifesto

Read the Blitz Manifesto to learn the Blitz foundational principles.

Blitz is built on Next.js. For more info on this see Why use Blitz instead of Next.js

Get in touch

The Blitz community is warm, safe, diverse, inclusive, and fun! Feel free to reach out to us in any of our communication channels.

Contributors

Thanks goes to these wonderful people (emoji key):


0xflotus

🖋

Talor Anderson

🐛

This project follows the all-contributors specification. Contributions of any kind welcome!

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].