Gitea Reviews

Parcel Reviews

Gitea mentions (60)

• Beware Offers of “Help” with Your Projects

  This reminds me of Gogs [0], where the original author refused a lot of good ideas and improvements, eventually leading to a fork [1] that's now a lot more popular and active than the original. [0] https://gogs.io/ [1] https://gitea.io/en-us/. - Source: Hacker News / about 1 year ago

• Incident with Issues and Pull Requests

  Yes, we do this using https://gitea.io/en-us/ on a private server. Firewall, backups and a replica running for most projects. Github is only used when it's required by a stakeholder. - Source: Hacker News / about 1 year ago

• Let's Make Sure GitHub Doesn't Become the Only Option

  There's a number of places out there, some of which also support alternatives to Git itself. By no means a complete list and in no particular order: GitLab - https://about.gitlab.com/ Sourcehut - https://sourcehut.org/ Codeberg - https://codeberg.org/ Launchpad - https://launchpad.net/ Debian Salsa - https://salsa.debian.org/public Pagure - https://pagure.io/pagure For self hsoted options, there's these below... - Source: Hacker News / about 1 year ago

• If you're on DSM 6 and still waiting for an update on the GitLab package, don't bother

  And if you need GitLab (for runner, etc...) then it's not too bad to run in Docker. But if anyone is looking for a somewhat simpler git solution, gitea is pretty great. Source: about 1 year ago

• OpenBSD Upgrade 7.2 to 7.3

  Check: Configuration and syntax changes and Special packages. The latter includes changes on PostgreSQL, Python and Gitea. - Source: dev.to / about 1 year ago

Parcel mentions (103)

• Create a typescript package with Parcel

  Parcel is a fast and zero-configuration web application bundler designed to simplify the build process for modern web projects. It's not limited to web applications, and it can be used to build packages targeting the browser or Node.js. - Source: dev.to / about 1 month ago

• How and why do we bundle zx?

  At first we wanted to just get rid of all the helper utilities. Keep only the kernel, but this would mean a loss of backward compatibility. We needed some efficient code processing instead with recomposition and tree-shaking. We needed a bundler. But which one? Our testing approach relies on targets, not sources. We rebuilt the project frequently, speed was critical requirement. In essence, we chose a solution... - Source: dev.to / about 2 months ago

• DEMO - Voice to PDF - Complete PDF documents with voice commands using the Claude 3 Opus API

  It runs using Parcel, very simple and easy to setup. The app has 3 files:. - Source: dev.to / about 2 months ago

• React Server Components Example with Next.js

  In the Changelog Podcast episode referenced above, Dan Abramov alluded to Parcel working on RSC support as well. I couldn’t find much to back up that claim aside from a GitHub issue discussing directives and a social media post by Devon Govett (creator of Parcel), so I can’t say for sure if Parcel is currently a viable option for developing with RSCs. - Source: dev.to / 2 months ago

• Build a Vite 5 backend integration with Flask

  Once you build a simple Vite backend integration, try not to complicate Vite's configuration unless you absolutely must. Vite has become one of the most popular bundlers in the frontend space, but it wasn't the first and it certainly won't be the last. In my 7 years of building for the web, I've used Grunt, Gulp, Webpack, esbuild, and Parcel. Snowpack and Rome came-and-went before I ever had a chance to try them.... - Source: dev.to / 4 months ago