karlkeefer / pngr Goto Github PK
View Code? Open in Web Editor NEWdockerized (postgres + nginx + golang + react)
License: MIT License
dockerized (postgres + nginx + golang + react)
License: MIT License
This router is potentially worth swapping in, so long as we can still pass things like current user as an argument to our handlers, and can stick in our own middleware...
should sketch out what continuous integration might look like
might as well be explicit
Hi! I just saw your HN post. You're right -- being able to just run docker-compose up
makes me a lot more inclined to start developing something new.
However, I'm reluctant to deploy my application to production using Docker. For the frontend I'd like to use something like Netlify for caching/web UI and for the backend I'd like to use something like App Engine for monitoring/scaling/etc
I feel like if you added an App Engine and Netlify configuration file, so you could clone the project and deploy to "production" in 2 commands, that would move this project to the next level :)
root/go/src/github.com/hashicorp/go-multierror/multierror.go:112:9: undefined: errors.As
root/go/src/github.com/hashicorp/go-multierror/multierror.go:117:9: undefined: errors.Is
root/go/src/github.com/golang-migrate/migrate/source/httpfs/partial_driver.go:148:6: undefined: errors.As
ERROR: Service 'postgres' failed to build: The command '/bin/sh -c go get -tags 'postgres' -u github.com/golang-migrate/migrate/cmd/migrate && cp /root/go/bin/migrate /bin/migrate' returned a non-zero code: 2
create-react-app and by extension craco is no longer recommended in React docs.
Here is a relevant comment from React maintainer Dan Abramov on shortcomings of create-react-app and it's future.
Lots of articles recommend switching to Vite and I switched to Vite in my project that I forked from this repo and it worked well for me. So I'd suggest moving in that direction.
I slammed this thing together, so I don't have tests on almost anything.
Bad!
Here is the migration guide. It's pretty straightforward.
I can probably take this on!
When the react image is being started it has to do a large npm install
, but puts out no logs, making it appear to be broken, especially since you just get a vague nginx error for well over a minute.
Create a useRequest helper to handle loading/error/data state, so that we can have more functional components!
v5 requires an update to Craco v7, but semantic-ui craco-less depends on craco 6.
No dice, yet.
npm install
makes it take forever for the react dev server to start.
Had to do it this way to avoid requiring container rebuild anytime you added a package... not sure if there's a better way.
Related issue: Probably should have helpers or documentation for running NPM commands in the container(!) for folks that don't have local npm setup and configured
random issues/ideas I had in a text file:
currently minified CSS is kludged into the front-end, but it would be fantastic improvement if folks could edit the semantic-ui variables, take advantage of the prebuilt semantic-ui themes, etc.
I'd like the ability to clone this repo, start hacking, push code to my repository and have a GitHub Actions pipeline run. The pipeline could be really simple, like just running my backend tests.
Being able to edit an existing GitHub Actions config file is way easier than trying to set everything up from scratch.
Otherwise people will get stuck on this relatively tricky configuration step.
I wanted to ask a couple of questions on how to do certain things but noticed discussions are not enabled for the repository.
Can we enable them?
Here is the link of how to do it.
Otherwise you could delete a user but their session token would remain valid indefinitely!
I think we could dramatically increase dev velocity by auto-generating our models/repos with sqlc!
Use this opportunity to fix/improve the migration file formats and helper scripts.
Should probably provides a step-by-step guide for actually forking this thing, setting up a VPS somewhere, basic configuration steps, etc.
It would be nice to flesh out a markdown file for this so that it stays with the project (vs. a medium post or something).
Vaguely related to CI #3
We ought to be able to configure nginx to redirect bots to a sidecar container running pre-render to give us "server-side rendering" for crawlers...
that way if you forget the https you still end up in the right place
Starting the app I received the following errors. I am typically a golang/backend dev and don't have a lot of React experience.
Is this something expected or easily addressed? I thought it was maybe an npm
issue and I ran npm install
in the react/
directory with no change.
I also looked at the npm package page and github page but both lack a README so there is no real guiding information there.
Compiled with problems:
ERROR in ./src/index.tsx 7:0-40
Module not found: Error: Can't resolve 'semantic-ui-less/semantic.less' in '/root/src'
ERROR in ./node_modules/@popperjs/core/lib/createPopper.js 1:0-63
Module not found: Error: Can't resolve './dom-utils/getCompositeRect.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/createPopper.js 2:0-57
Module not found: Error: Can't resolve './dom-utils/getLayoutRect.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/createPopper.js 3:0-65
Module not found: Error: Can't resolve './dom-utils/listScrollParents.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/createPopper.js 4:0-61
Module not found: Error: Can't resolve './dom-utils/getOffsetParent.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/createPopper.js 5:0-63
Module not found: Error: Can't resolve './dom-utils/getComputedStyle.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/createPopper.js 6:0-55
Module not found: Error: Can't resolve './utils/orderModifiers.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/createPopper.js 7:0-43
Module not found: Error: Can't resolve './utils/debounce.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/createPopper.js 8:0-61
Module not found: Error: Can't resolve './utils/validateModifiers.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/createPopper.js 9:0-43
Module not found: Error: Can't resolve './utils/uniqueBy.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/createPopper.js 10:0-59
Module not found: Error: Can't resolve './utils/getBasePlacement.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/createPopper.js 11:0-49
Module not found: Error: Can't resolve './utils/mergeByName.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/createPopper.js 12:0-55
Module not found: Error: Can't resolve './utils/detectOverflow.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/createPopper.js 13:0-54
Module not found: Error: Can't resolve './dom-utils/instanceOf.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/index.js 2:0-37
Module not found: Error: Can't resolve './modifiers/index.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/index.js 4:0-102
export 'detectOverflow' (reexported as 'detectOverflow') was not found in './createPopper.js' (possible exports: createPopper, popperGenerator)
ERROR in ./node_modules/@popperjs/core/lib/popper-lite.js 2:0-59
Module not found: Error: Can't resolve './modifiers/eventListeners.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/popper-lite.js 3:0-57
Module not found: Error: Can't resolve './modifiers/popperOffsets.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/popper-lite.js 4:0-57
Module not found: Error: Can't resolve './modifiers/computeStyles.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/popper-lite.js 5:0-53
Module not found: Error: Can't resolve './modifiers/applyStyles.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/popper-lite.js 11:0-75
export 'detectOverflow' (reexported as 'detectOverflow') was not found in './createPopper.js' (possible exports: createPopper, popperGenerator)
ERROR in ./node_modules/@popperjs/core/lib/popper.js 2:0-59
Module not found: Error: Can't resolve './modifiers/eventListeners.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/popper.js 3:0-57
Module not found: Error: Can't resolve './modifiers/popperOffsets.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/popper.js 4:0-57
Module not found: Error: Can't resolve './modifiers/computeStyles.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/popper.js 5:0-53
Module not found: Error: Can't resolve './modifiers/applyStyles.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/popper.js 6:0-43
Module not found: Error: Can't resolve './modifiers/offset.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/popper.js 7:0-39
Module not found: Error: Can't resolve './modifiers/flip.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/popper.js 8:0-61
Module not found: Error: Can't resolve './modifiers/preventOverflow.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/popper.js 9:0-41
Module not found: Error: Can't resolve './modifiers/arrow.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/popper.js 10:0-39
Module not found: Error: Can't resolve './modifiers/hide.js' in '/root/node_modules/@popperjs/core/lib'
ERROR in ./node_modules/@popperjs/core/lib/popper.js 16:0-75
export 'detectOverflow' (reexported as 'detectOverflow') was not found in './createPopper.js' (possible exports: createPopper, popperGenerator)
ERROR in ./node_modules/@popperjs/core/lib/popper.js 20:0-37
Module not found: Error: Can't resolve './modifiers/index.js' in '/root/node_modules/@popperjs/core/lib'
ERROR
[eslint]
src/index.tsx
Line 5:8: Unable to resolve path to module 'semantic-ui-less/semantic.less' import/no-unresolved
Search for the keywords to learn more about each error.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.