parsemail
action-hosting-deploy
Our great sponsors
parsemail | action-hosting-deploy | |
---|---|---|
59 | 8 | |
2 | 652 | |
- | 2.3% | |
2.9 | 2.9 | |
about 2 months ago | 10 days ago | |
Go | TypeScript | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
parsemail
-
G Suite legacy free edition accounts being suspended on July 1, 2022
It's a pain in the ass right now. Original I come up with the domain hanami.run because I explained here https://www.youtube.com/watch?v=O1p2crPpFIc I feel like wind blow flowers where Hanami blow out emails.
- Ask HN: Those making $500/month on side projects in 2021 – Show and tell
-
IP for mail server
I run an email forwarding services (https://hanami.run if you want to check it out) and I can share some info:
-
Ask HN: Great tools for solo SaaS founders?
I found https://hanami.run (soon to be mailwip.com due to name conflict with hanamirb.org) to setup email forwarding and a simple blog platform by "email to post" and webhook.
Use it you can consolidate emails from multiple domains to forward to the same inbox. And you can add webhook/slack notification too.
-
Truth about ProtonMail
You can look into mine (https://hanami.run) very fast to sign up and have a few cool features about webhook or smtp.
Also, improvmx.com is a great product as well.
If you like open source, https://maddy.email/ is a single binary deployment that can handle everything even IMAP.
https://mailcow.github.io/mailcow-dockerized-docs/ is a dockerize solution with super detail document as well.
-
How to Create a SaaS and Compete with the Big Players as a Solo Founder
If you want to compete with the big players, you have to solve the most important pain point and work upward from that small use base.
My case: I work on https://hanami.run (will soon move to https://mailwip.com due to hanamirb.org conflict) and email forwarding is very competitive. Big and old players are all over the place because at the end of day, setting up email forwarding isn't hard and many open source project did it, heck you can spin up AWS lambda for incoming email in no time.
The pain point is: email will drop sometime, time to time no matter how good an email forwarding service is because they have to scan spam, have false positive, or because of strict DMARC/SPF rule. And I have no tools available to help me out there. So I focus strongly on my maillog features with many level of privacy:
- no log at all
-
Ask HN: Solo-preneurs, how do you DevOps to save time?
- docker-compose to spin up everything. It's super nice. Again, the deployment is done with a `rsync` then `docker-compose up -f docker-compose-prod.yml`
Eventually when deployment changes very frequent and need scale/ha I added in Kubernetes. K8S is way easiser to setup than you think and it handle all other suff(load balancer, environment variable etc).
And my deploy now become: `kubectl apply -f`
One trick I used is to use `sed` or `envsubst` to replace the image hash.
For backedup, I again, literally setup cronjob from an external server, `ssh` into database and run `pgdump`.
I also have a nice NFS server to centralize config and sync back to our git repo.
I used this whole setup to operate https://hanami.run an email forwarding service for the first 3 months before I added Kubernetes.
-
When users never use the features they asked for
So I want to share a story about user asking for a feature then not using it.
I run an email forwarding services(https://hanami.run) basically you add your domains in and add some records.
We had this one heavy users who has like hundreds of domains. So our UI isn't design for that. Who has hundreds of domains? So they approach and asked us for a way to organize those domains into a hierarchy structure.
All good.
They are paid our highest tier ($30 per month) so we prioritize the requests and work on it.
2 days later that same user downgrade to the lowest plan and delete all of their hundred of domains...
That complicated features remain unused to nowadays...
-
Easily creating and routing email addresses with Cloudflare Email Routing
I used hanami.run and they support that. A catch-all then an explicitly deny rule to disable certain address.
-
Is it possible to setup email forwarding from a domain brought from Wix
Wix doesn't have built-in email forwarding but you can use any email forwarding service. Look into hanami.run and simply follow their onboarding process to add your MX record. https://hanami.run/docs/configure_dns#mx
action-hosting-deploy
-
What are the best practices to hide sensitive information in your open source project
Could they not have their own FB to develop against? Does every dev need to use just yours? If that is the case, then you'd need to use https://support.google.com/firebase/answer/7000272?hl=en also, it looks to be possible to include Firebase in your GitHub for them to pull from https://firebase.google.com/docs/hosting/github-integration
-
Anyone interested in a website that allows pushing to Firebase Hosting in just a couple of clicks?
Github Actions is the way to go for this: https://firebase.google.com/docs/hosting/github-integration
-
Taiga UI: A year in Open Source
Whenever a Pull Request is created we need to be able to quickly checkout the changes. Reading code diff is great, but sometimes you just need to tinker with the new version, test it on mobile, different browsers and OS. Cloud services are perfect for this case, they allow you to deploy the code temporarily and access it with a link from any device. We chose Firebase to host it for us and a Github action posts a link to the deployment as a comment in the Pull Request. It works like a charm and speeds up code reviews a lot. Read this article to set it up on your repository!
- Firebase: Deploy to live and preview channels via GitHub pull requests
-
Ask HN: Solo-preneurs, how do you DevOps to save time?
Lambdas and firebase on the GCP stack for CRUD apps.
One nice thing about firebase -> each PR deploys to its own preview channel[1].
Downside: Very JS heavy. I write lambdas in python though.
[1] https://firebase.google.com/docs/hosting/github-integration
-
Autodeploy subdirectory to Firebase
Google Firebase has a pretty straightforward guide to setting up auto-deploy from Github, which you can take a look at here: https://firebase.google.com/docs/hosting/github-integration
-
[Help] First time setting up Github (actions?) for Firebase Functions
What is the easiest way for setting up CI/CD from GH for Firebase functions? Maybe something like this for hosting, but only for functions?
-
3 steps for handling GitHub Workflow Secrets
Note: you can find more info about the used steps actions here actions/checkout@v2 and here FirebaseExtended/action-hosting-deploy@v0
What are some alternatives?
mailway - Mailway installer, host your own Mailway instance
firebase-tools - The Firebase Command Line Tools
GoAccess - GoAccess is a real-time web log analyzer and interactive viewer that runs in a terminal in *nix systems or through your browser.
flyctl - Command line tools for fly.io services
portmaster - 🏔 Love Freedom - ❌ Block Mass Surveillance
golang-samples - Sample apps and code written for Google Cloud in the Go programming language.
caniemail - Can I email… Support tables for HTML and CSS in emails.
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
mailcheck - Reduce misspelled email addresses in your web apps.
ngx-scully-blog - A simple blog made for developers that is easy to setup, supports SEO, Google Adsense, Google Analytics, Facebook Pixel, and many more
s6-overlay - s6 overlay for containers (includes execline, s6-linux-utils & a custom init)
laravel-backup - A package to backup your Laravel app