Crisp

crisp

The emergence of remarkable technologies like the Internet, the iPhone, and Bitcoin have left us all in constant search of "the next big thing."Is it Uber? Airbnb? Everything-as-a-service? Tesla? Gartner formalized this frenzied questioning with the " ." hype cycle One trend Gartner notes is the rise of the "augmented human," which, besides improving the human body with biochips and AI, includes biotech, like CRISPR. CRISPR is a gene editing tool, combining a guide RNA (molecular GPS) with a Cas endonuclease (molecular scissors) to let us finely target and manipulate genes at will. Infinite Possibility Because there are many kinds of , there are many applications for CRISPR, including , , , and . Cas endonucleases COVID-19 testing HIV diagnostics autism treatments so much more The sheer versatility of a precise gene manipulation tool like CRISPR means the sky is the limit. One of Silicon Valley's most marquee brands, YCombinator, writes about how genetically engineered ocean phytoplankton could . Yes, CRISPR can be used here . solve climate change as well Infinite Risk? Like Uncle Ben said, with great power comes great responsibility. While clichés like this are thrown around constantly, whether it's in AI or even blockchain, the reality is that CRISPR truly is a turning point for humanity. There's a nearly-universal of CRISPR for non-therapeautic uses, like creating designer babies: denouncement "In our view, genome editing in human embryos using current technologies could have unpredictable effects on future generations... This makes it dangerous and ethically unacceptable." The more politically correct term is "genetically modified children," which is accomplished through human germline editing, or changing heritable DNA (sperm and eggs, or embryos). If scientists edit heritable DNA, it's something we can't take back. This is in sharp contrast to most other technologies out there. For instance, if you unintentionally create a biased AI algorithm, there will be and potentially , but the algorithm can be rolled-back and modified. a ton of backlash fear You can't roll-back a line of genetically-modified humans (or any other animal, for that matter). Once they're out of the lab, genetically modified organisms are free to reproduce, and continue passing on manipulated genes, with unforeseeable consequences. The solution seems fairly straightforward: A moratorium on heritable DNA editing, while allowing somatic DNA editing (not sperm and egg cells). However, we're not out of the water just yet. A Fight to Control CRISPR With so much at stake, many parties are engaged in vicious legal battles to . patent CRISPR Since the first commercialization of CRISPR Cas9 in 2012, hundreds upon hundreds of patent applications have been made, leading to many disputes and overlaps in claimed IP. This is a sign that, while an incredibly powerful technology, we're still in the early days of the CRISPR field. By comparison, the AI and blockchain industries, for instance, are not wholly embroiled in patent battles over technological control. Instead, we're seeing and being used around us already. blockchain AI The Future of CRISPR Once the legal battles over CRISPR settle down, rapid progress will be inevitable. Even now, we're seeing tremendous developments being made. While CRISPR now is mostly limited to university labs and scientists, this technology is being " ," or more simply, it's becoming more and more accessible. democratized To become a part of that democratization and help advance the field for everyone, not just those at the top, it's up to readers like you to . learn more about CRISPR

Why CRISPR Deserves the Hype

Casting the Tablets: CRISPR

It’s now been 18 months since we started mabl with an effort to help make test automation easier for software teams around the world. As we’ve come this far, we’ve tried to , engaging them in our channel, with user surveys, and meeting them at conferences throughout the world. All of this engagement has helped shaped the mabl product into what it is today with dozens of customers adopting it as their primary automated testing service. stay as close as possible to our users Friends of mabl slack Even with all of these endeavors, we believe there’s more we can do for software teams and the testing community broadly than just listening closely and building a product. We decided it was time to: engage with teams more actively broaden the scope of the feedback from the community back into the mabl product build further awareness of the trends within testing teams around continuous delivery. 1) 2) 3) That’s why we’re super excited to welcome Lisa Crispin to the mabl team. Many of you have been curious what Lisa’s title would be and what she’d be doing so I thought I’d share some more details. What’s Lisa’s role at mabl? At the heart of Lisa’s focus will be what she’s been doing for a lifetime — publicly sharing her experience and learnings with the testing community through public speaking opportunities at conferences like , conference, and other Testing events around the world. Despite working at mabl, she will not focus on mabl, but instead continue to focus on agile, , and how teams adopting these trends can improve their testing processes. We’ll also leverage Lisa’s public speaking experience at other smaller events including Meetups and to extend her reach to audiences who don’t get to extend to the larger conferences. Agile Testing Days CAST continuous delivery DevOpsDays Lisa’s reputation has been established as a practitioner in the testing community, especially as it relates to Agile development practices, and that’s one focus she’ll continue to have. We are offering Lisa’s expertise to mabl clients throughout the world to both learn from her experience in how to make testing more effective but for Lisa to also learn from their experiences on what makes effective software delivery. This will be a two-way learning experience so both client and Lisa will draw value from one another in an effort to improve testing process and quality for users globally. Community Engagement As we’ve learned through the key features we’ve built already, much of our roadmap is shaped by our users. , File Upload, and items in tests have all been suggestions from our users. However these are only the tip of the iceberg of features we could be building into mabl. Data-driven testing Asserting on Not Present Lisa will engage with not only mabl users, but with the community broadly to solicit feedback and help prioritize the features which make automated testing easier. To date, we’ve done this with the extra time our team has had, but Lisa will engage more closely with our users and the community to truly understand the use cases and challenges they have today. She’ll explore the broader themes that we could build into mabl, and also dive deeper into where machine learning could help with some of the more manual tasks testers have today. Lisa’s goal here is to accelerate innovation in the test automation lifecycle. To kick things off, she’s hosting her first mabl webinar next month. Lisa will help you learn the language of DevOps and continuous delivery so that you can communicate better with your team. You’ll see examples to better understand continuous delivery and continuous deployment pipelines. Lisa will introduce some tools and techniques that can help your team embrace a DevOps culture, and learn how testers can help build bridges between “Dev”, “Ops” and the business stakeholders. You’ll learn that there IS a “test” in “DevOps” — what we’re calling DevTestOps. Moving Forward As you may be able to tell, we’ve put a lot of thought into how Lisa can help the testing community while also driving innovation in test automation. If you have suggestions for other ways Lisa could be helpful to you, we’d love to hear your feedback! Lisa is now officially on board and her title is but we just refer to her as a member of the mabl team. Feel free to find her on or . Testing Advocate, Slack Twitter Originally published at www.mabl.com .

Lisa Crispin teams up with mabl to drive innovation in test automation

Baptiste is the CEO and co-founder of Crisp, an easy and effective way to chat with your website visitors. Davis Baer : What’s your background, and what are you working on? : My name is Baptiste Jamin, and I’m 24, and I’m CEO at Crisp. My passion for hacking things started when I was 5: My brother taught me how to boot our family’s Windows 3.1 computer using DOS. Then, when I was 12 I started coding by joining open source projects as a developer. We made indie video games, 2D games engines. At this time, Github didn’t exist and it’s crazy how we made projects as teenagers just by searching for knowledge on internet. This how my passion with entrepreneurship came. Baptiste Jamin Then, after being fired in High School because I hacked the network system, I joined a networking school. I also joined Orange the biggest ISP as a developer as a part-time job, did some freelancing, and joined few startups as a developer. During this time, I also did few side projects: Some succeeded, others failed. Later, I met Valerian, my now co-founder at Crisp. When I met him, he was working on an open source messaging solution using XMPP which was used by NATO and 60K users. On my end, I was working on trash mail system, which was popular in France also. From our previous side projects and startup experiences, we truly felt it was crucial to communicate with customers to succeed instartups, and at this time, most tools were outdated, complex and expensive for small companies. So we made it easy for startups and small companies to chat with their customers and to unify all their customer relationship in one place. They can add our chat on their website, manage all their customer email, Facebook Messenger queries, from our tool. Now, around 70K websites are using Crisp, around 60 million people are chatting every month on the platform. What went into building the initial product? In 2015, we kickstarted Crisp in three months in my cofounder’s flat in France. First, we designing the platform on Sketch, and then literally coded the platform in a few weeks, using a micro-service architecture and an AngularJS app. It was my first time ever working with this new co-founder. Then we started getting our first users. The fun story about this, is that a good friend of mine wanted wanted to try the platform, and it was password-locked. He asked me to remove the password lock. So I did. A day later, we discovered that around 20 users were using the product and were happy with it! This friend had been sent an angry email because they didn’t have any customer support chat, and they wanted to use Crisp to solve this. A bit later, one of those customers posted us on ProductHunt, and this is how our growth started. The first Crisp release. At this time the product was free, and I guess it helped to get an initial traction and to learn about the market. When you are free, customers are also a bit more tolerant about the lack of features on the product. Being free also forced us to optimize everything, because at this time we didn’t have any money. For instance I had to sell my car and few other things I had so I could focus on Crisp full-time. By optimizing, we had to optimize each dollar, and we coded internal tools like our own help-center, status page, financial tools. The funny thing is our customer loved those tools, and asked us to release these as products later. We also had to go really fast because the competition was also moving quickly, so we had to implement a ton of new features in a small amount of time. We were a really small team(two founders — developers), and thanks to all our previous experience we were able to move fast. We also chose to bootstrap instead of fundraise. Thanks to this decision, we are 100% independent. How have you attracted users and grown Crisp? After we got our first traction thanks to my friend and ProductHunt, we did a lot of growth hacking. We had to optimize our landing page and our app to convert visitors to long term users. For instance we discovered that when people implemented Crisp onto their website after signing up, 51% were still using the platform after 10 weeks. So we doubled down on how to make people install Crisp on their website. It was a big technical and UX challenge. What helped a lot as well, was the “Powered by Crisp” logo under our chatbox that amplified the growth as well. Finally, the most important advice to entrepreneurs is to focus on customers and customers support. This is the most important thing to grow. Thanks to customers, you will learn how to improve your product. What’s your business model, and how have you grown your revenue? As explained earlier, we started by being free. The free customers helped us to know what were the most imported paid features to build. A year after launching Crisp, we released Crisp 2.0 on ProductHunt with our new paid model with the new paid features (we still have a free plan). In a few days, we had a huge success. Crisp has a very international base, so we had to implement most of payment providers out there. This is why we are using both Stripe and PayPal as payment options. The key of our success is we adapted our pricing for startups, and we have a plan for each situation, from new startups to succeeding companies. What are your goals for the future? Currently we are working on a new release on Crisp that should be out there soon. The goal is to double our annual revenue and customers in the next few year. Personally, we will also start being sedentary again, after being nomads for so long. Crisp is still a small team (we are now 5), and bootstrapping our company allowed us to be nomads.Over the last few years, we moved to several different locations. Sometimes we are with each other, sometimes we are not. I also lived with my cofounder for several months. What are the biggest challenges you’ve faced and obstacles you’ve overcome? If you had to start over, what would you do differently? The biggest challenge was clearing how to build a big platform in a small amount of time. If I started Crisp again, I wouldn’t change anything, even mistakes can lead to luck, and that’s what happened. Young entrepreneurs who are doing their first project don’t even realize how it helps to know nothing (yet) about the subject you are working on. Have you found anything particularly helpful or advantageous? We had some help and knowledge about The Family. I would say it’s the French YC, which we were a part of. It helped us to meet interesting people and to focus on growth. For instance, I didn’t even know what SaaS meant before meeting people from The Family. What’s your advice for entrepreneurs who are just starting out? The best advice is to work hard, and to build to the best of your abilities. I also think that young entrepreneurs should build side projects to get some experiences before building a startup. You can build really successful projects, that are not startups, but that could be in the future. I think it’s what happened to Crisp. Where can we go to learn more? You can learn more about Crisp on and by . crisp.chat following Crisp on twitter Don’t hesitate to comment this post if you want to know more about us. This interview is brought to you by , a tool to schedule and automatically repeat your posts on Facebook, Instagram, Twitter, Pinterest, LinkedIn, and Google My Business OneUp

Founder Interviews: Baptiste Jamin of Crisp

Building Vertical SaaS in an Old School Industry: What NOT to Do

Mä Nayra Yatiqañ Utan Industrian SaaS Vertical luraña: Kuns JANIW lurañakiti

একটি পুরানো স্কুল শিল্পে উল্লম্ব SaaS নির্মাণ: কি করা উচিত নয়

Cómo crear SaaS vertical en una industria tradicional: qué NO hacer

Izgradnja vertikalnog SaaS-a u industriji stare škole: Što NE činiti

Vertikális SaaS építése egy régi iskolai iparágban: mit NE tegyünk

旧来の業界で垂直型 SaaS を構築する: やってはいけないこと

ການກໍ່ສ້າງ SaaS ແນວຕັ້ງຢູ່ໃນອຸດສາຫະກໍາໂຮງຮຽນເກົ່າ: ສິ່ງທີ່ບໍ່ຄວນເຮັດ

Vertikāla SaaS izveide vecās skolas nozarē: ko NEDRĪKST darīt

पुरानो विद्यालय उद्योगमा ठाडो SaaS निर्माण गर्दै: के नगर्ने

Kujenga SaaS Wima katika Sekta ya Shule ya Zamani: Nini Usifanye

Köne mekdep pudagynda dik SaaS gurmak: Näme etmeli däl

پرانی اسکول کی صنعت میں عمودی ساس بنانا: کیا نہیں کرنا ہے۔

The iOS Guide to Haptic Feedback

In this article I will show you how to deploy django to production. We will be using nginx, gunicorn and cloudflare tunnels. I recently deployed my very own django application to production. The website is called videiro.com and was developed in django + HTML/CSS/JS + Tailwind. Setup I am using a debian 12 server which will expose my application via cloudflare tunnels. All of the static files are being served via nginx and the Django project is being ran by gunicorn. In this guide I will show you how I set this up. Preparing the Django project¶ The first thing you will have to do is open the settings.py and change the following Debug = False
ALLOWED_HOSTS = ['yourdomain.tld']
CSRF_COOKIE_SECURE = True
CSRF_TRUSTED_ORIGINS = [
    'yourdomain.tld',
] You should also change the SECRET_KEY to a long random string, that you should never share with anyone. After that create a new file called .gitignore and paste the following: db.sqlite3
*.pyc This will make sure that the database is not uploaded to our server and that no pyc files are either. Now you can upload your project to a new github repository (or gitea repository). If you don’t want everyone to have access to your source code make sure to set the repository as private. If you want to make sure that your source code stays private I recommend you setup a selfhosted gitea instance, read Selfhost your own gitea instance - selfhosted, lightweight github alternative, to learn how to do that. git init
git branch -M main
git add .
git commit -m "initial commit"
git remote add origin https://...
git push -u origin main Now that you we have done that you should login to your server Server setup Before configuring anything make sure that you don’t allow any ssh logins with a password. Follow Securing ssh with Key-Based authentication to secure your server from those kinds of attacks. Login to your server ssh user@server.ip Make sure that your packages are up to data sudo apt update && sudo apt upgrade Now install python, pip, git and nginx sudo apt install python3 python3-pip git nginx Now clone your project into your home directory. git clone https://...
cd my-project Once you’re in install the following: pip install django django-crispy-forms Now try to run the project: python3 manage.py runserver If you get an error that a package is missing install it and re run. Configuring gunicorn Now we will setup gunicorn. First install it pip install gunicorn Now create a new file called gunicorn.service with your favorite text editor: sudo vim /etc/systemd/system/gunicorn.service And paste the following: [Unit]
Description=gunicorn daemon
After=network.target

[Service]
User=YOURUSER
Group=www-data
WorkingDirectory=/home/YOURUSER/PROJECT
ExecStart=/path/to/gunicorn --access-logfile - --workers 3 --bind 127.0.0.1:8000 PROJECTNAME.wsgi:application

[Install]
WantedBy=multi-user.target Change YOURUSER to your user. To find the path to gunicorn run: which gunicorn And your project name is the name of the folder inside of your project that contains the settings.py file. Now run the following commands to start and enable gunicorn (start on boot) sudo systemctl daemon-reload
sudo systemctl start gunicorn.service
sudo systemctl enable gunicorn.service Now if you head to 127.0.0.1:8000 you should see your project running. But we’re not finished yet Setting up nginx Now we need to serve our static content via nginx. First create a new file nginx configuration file with your favorite text editor: sudo vim /etc/nginx/sites-available/PROJECT Change PROJECT to whatever you want Now paste the following content: server {
    listen 80;
    server_name YOURDOMAIN;

    location /static/ {
	alias /var/www/staticfiles/;
    }

    location / {
        proxy_pass http://127.0.0.1:8000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
} Just change YOURDOMAIN to the domain that this will be hosted on. Create a symbolic link to enable your website: sudo ln -s /etc/nginx/sites-available/PROJECT /etc/nginx/sites-enabled/ Start and enable nginx: sudo systemctl start nginx
sudo systemctl enable nginx Setup static files The first thing you will have to do is cd into your (django) project cd project Now run the following command: python3 manage.py collectstatic This will create a new folder called staticfiles Now to set up the static files we have two options: Change the user in /etc/nginx/nginx.conf to your user (less secure)
Copy over the staticfiles to /var/www/ (more secure) I will be doing the 2nd option: First create a new file called staticfiles in /var/www sudo mkdir -p /var/www/staticfiles Now copy over all of the staticfiles from your project there: sudo cp staticfiles/* /var/www/staticfiles Now cd into /var/www cd /var/www Change the ownership of all the files sudo chown www-data:www-data staticfiles
sudo chown www-data:www-data staticfiles/* Restart the nginx service: sudo systemctl restart nginx Now if you head to: 127.0.0.1 You should see your website running with all of the static files being served! Exposing via cloudflare tunnels Now to make your website publicly accessible. To do this you will need a cloudflare account and a domain pointed to cloudflare. First head to the Zero Trust Dashboard Under Networks click on Tunnels and then Create a tunnel Once created you should Install and run a connector, follow the instructions on the page for your specific setup. After the connector is running you should click on the Public Hostname tab and Add a public hostname. Now you should see something like this: Fill in the info as I have. The service type should be HTTP and the url should be 127.0.0.1:80 or localhost:80 Now if you head to the domain that you specified you should see your app up and running. Congratulations! If you enjoyed this post and want to support my (mostly unpaid) work , you can donate here. Join my free newsletter Here: https://newsletter.4rkal.com/subscription/form In this article I will show you how to deploy django to production. We will be using nginx, gunicorn and cloudflare tunnels. I recently deployed my very own django application to production. The website is called videiro.com and was developed in django + HTML/CSS/JS + Tailwind. videiro.com Setup I am using a debian 12 server which will expose my application via cloudflare tunnels. All of the static files are being served via nginx and the Django project is being ran by gunicorn. In this guide I will show you how I set this up. Preparing the Django project ¶ ¶ The first thing you will have to do is open the settings.py and change the following Debug = False
ALLOWED_HOSTS = ['yourdomain.tld']
CSRF_COOKIE_SECURE = True
CSRF_TRUSTED_ORIGINS = [
    'yourdomain.tld',
] Debug = False
ALLOWED_HOSTS = ['yourdomain.tld']
CSRF_COOKIE_SECURE = True
CSRF_TRUSTED_ORIGINS = [
    'yourdomain.tld',
] You should also change the SECRET_KEY to a long random string, that you should never share with anyone. SECRET_KEY After that create a new file called .gitignore and paste the following: .gitignore db.sqlite3
*.pyc db.sqlite3
*.pyc This will make sure that the database is not uploaded to our server and that no pyc files are either. Now you can upload your project to a new github repository (or gitea repository). If you don’t want everyone to have access to your source code make sure to set the repository as private. If you want to make sure that your source code stays private I recommend you setup a selfhosted gitea instance, read Selfhost your own gitea instance - selfhosted, lightweight github alternative , to learn how to do that. Selfhost your own gitea instance - selfhosted, lightweight github alternative git init
git branch -M main
git add .
git commit -m "initial commit"
git remote add origin https://...
git push -u origin main git init
git branch -M main
git add .
git commit -m "initial commit"
git remote add origin https://...
git push -u origin main Now that you we have done that you should login to your server Server setup Before configuring anything make sure that you don’t allow any ssh logins with a password. Follow Securing ssh with Key-Based authentication to secure your server from those kinds of attacks. Securing ssh with Key-Based authentication Login to your server ssh user@server.ip ssh user@server.ip Make sure that your packages are up to data sudo apt update && sudo apt upgrade sudo apt update && sudo apt upgrade Now install python, pip, git and nginx sudo apt install python3 python3-pip git nginx sudo apt install python3 python3-pip git nginx Now clone your project into your home directory. git clone https://...
cd my-project git clone https://...
cd my-project Once you’re in install the following: pip install django django-crispy-forms pip install django django-crispy-forms Now try to run the project: python3 manage.py runserver python3 manage.py runserver If you get an error that a package is missing install it and re run. Configuring gunicorn Now we will setup gunicorn. First install it pip install gunicorn pip install gunicorn Now create a new file called gunicorn.service with your favorite text editor: sudo vim /etc/systemd/system/gunicorn.service sudo vim /etc/systemd/system/gunicorn.service And paste the following: [Unit]
Description=gunicorn daemon
After=network.target

[Service]
User=YOURUSER
Group=www-data
WorkingDirectory=/home/YOURUSER/PROJECT
ExecStart=/path/to/gunicorn --access-logfile - --workers 3 --bind 127.0.0.1:8000 PROJECTNAME.wsgi:application

[Install]
WantedBy=multi-user.target [Unit]
Description=gunicorn daemon
After=network.target

[Service]
User=YOURUSER
Group=www-data
WorkingDirectory=/home/YOURUSER/PROJECT
ExecStart=/path/to/gunicorn --access-logfile - --workers 3 --bind 127.0.0.1:8000 PROJECTNAME.wsgi:application

[Install]
WantedBy=multi-user.target Change YOURUSER to your user. YOURUSER To find the path to gunicorn run: gunicorn which gunicorn which gunicorn And your project name is the name of the folder inside of your project that contains the settings.py file. settings.py Now run the following commands to start and enable gunicorn (start on boot) sudo systemctl daemon-reload
sudo systemctl start gunicorn.service
sudo systemctl enable gunicorn.service sudo systemctl daemon-reload
sudo systemctl start gunicorn.service
sudo systemctl enable gunicorn.service Now if you head to 127.0.0.1:8000 you should see your project running. But we’re not finished yet Setting up nginx Now we need to serve our static content via nginx. First create a new file nginx configuration file with your favorite text editor: sudo vim /etc/nginx/sites-available/PROJECT sudo vim /etc/nginx/sites-available/PROJECT Change PROJECT to whatever you want Now paste the following content: server {
    listen 80;
    server_name YOURDOMAIN;

    location /static/ {
	alias /var/www/staticfiles/;
    }

    location / {
        proxy_pass http://127.0.0.1:8000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
} server {
    listen 80;
    server_name YOURDOMAIN;

    location /static/ {
	alias /var/www/staticfiles/;
    }

    location / {
        proxy_pass http://127.0.0.1:8000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
} Just change YOURDOMAIN to the domain that this will be hosted on. Create a symbolic link to enable your website: sudo ln -s /etc/nginx/sites-available/PROJECT /etc/nginx/sites-enabled/ sudo ln -s /etc/nginx/sites-available/PROJECT /etc/nginx/sites-enabled/ Start and enable nginx: sudo systemctl start nginx
sudo systemctl enable nginx sudo systemctl start nginx
sudo systemctl enable nginx Setup static files The first thing you will have to do is cd into your (django) project cd project cd project Now run the following command: python3 manage.py collectstatic python3 manage.py collectstatic This will create a new folder called staticfiles staticfiles Now to set up the static files we have two options: Change the user in /etc/nginx/nginx.conf to your user (less secure) Copy over the staticfiles to /var/www/ (more secure) Change the user in /etc/nginx/nginx.conf to your user (less secure) /etc/nginx/nginx.conf Copy over the staticfiles to /var/www/ (more secure) /var/www/ I will be doing the 2nd option: First create a new file called staticfiles in /var/www sudo mkdir -p /var/www/staticfiles sudo mkdir -p /var/www/staticfiles Now copy over all of the staticfiles from your project there: sudo cp staticfiles/* /var/www/staticfiles sudo cp staticfiles/* /var/www/staticfiles Now cd into /var/www cd /var/www cd /var/www Change the ownership of all the files sudo chown www-data:www-data staticfiles
sudo chown www-data:www-data staticfiles/* sudo chown www-data:www-data staticfiles
sudo chown www-data:www-data staticfiles/* Restart the nginx service: sudo systemctl restart nginx sudo systemctl restart nginx Now if you head to: 127.0.0.1 127.0.0.1 You should see your website running with all of the static files being served! Exposing via cloudflare tunnels Now to make your website publicly accessible. To do this you will need a cloudflare account and a domain pointed to cloudflare. First head to the Zero Trust Dashboard Zero Trust Dashboard Under Networks click on Tunnels and then Create a tunnel Networks Tunnels Create a tunnel Once created you should Install and run a connector , follow the instructions on the page for your specific setup. Install and run a connector After the connector is running you should click on the Public Hostname tab and Add a public hostname . Public Hostname Add a public hostname Now you should see something like this: Fill in the info as I have. The service type should be HTTP and the url should be 127.0.0.1:80 or localhost:80 HTTP 127.0.0.1:80 localhost:80 Now if you head to the domain that you specified you should see your app up and running. Congratulations! If you enjoyed this post and want to support my (mostly unpaid) work , you can donate here. If you enjoyed this post and want to support my (mostly unpaid) work , you can donate here . donate here Join my free newsletter Here: https://newsletter.4rkal.com/subscription/form https://newsletter.4rkal.com/subscription/form

How To Deploy Django to Production

It's been a long old slog to get here (8 months in fact). Here's rough timeline of what the last 8 months have looked like: Month 1 - validation: My tool called Basefront - basefront.app is within the Airtable space (it's a tool to create directories, galleries and job boards with airtable data that you can integrate on any site) and I had already built up an audience in this space. In order to get validation before I actually went ahead and built the thing I set myself a goal of getting 10 presales at heavily discounted rate. I managed to get 12 presales before the initial MVP went live and this for me was enough validation to build. At this point total revenue was around $450. Months 2-5 - build: Surprise, surprise, this actually took alot longer than the 1 month I initially planned, more like 3 months. There was just no way round it. Working with the airtable API and creating the customization features I had planned meant this was a hefty build and thats with stripping things back like user groups, paywalls etc etc. I built the tool in bubble using nocode but essentially I use it to then create the code my users then add to their stack. I used Claude (anthropic) alot for the code part of things - massive help. Month 6 - 'We're live in beta' My first email went out to my existing list and this was an exciting and nerve wracking time. My list wasn't massive so my plan was to essentially use this phase as beta testing. The tool has a free plan and I made it clear we were in beta. I also asked everyone who used the tool if they would be happy to provide feedback for 3 months of full access PRO plan. I managed to get some great feedback, but honestly it's painful, of 160 or so people on my list, about 30 tried it and 5 came back with helpful feedback and by the end of this month I also managed to get another 4 paid users signed up (who interestingly preferred to pay than to offer feedback in return for PRO access). Revenue at this point was close to $600. Month 7 - 'fix as much stuff as possible' There's always going to be things that slip through the net and bugs that popup. I knew if I could just get the product to a 'useable' and 'enjoyable' state that my users wouldn't mind about a few small bugs and fixes (especially as I made it clear I was in beta). I Built a simple logging process to track common user activity (creating, editing deleting etc) and this gave me valuable insight into any issues that were arising. I should have probably added something like hotjar for even better insight (this is on my list still). [It's worth noting that as soon my product was in beta I also did marketing every week day for at least 1 hr] So by this point I had done nearly 8 weeks of marketing and the compounding effects started to take place, I was getting on average 2 free users sign up a day (around 60 per month). I got another 5 pro users sign up this month a few on annual so my total revenue at this point was around $780. Month 8 - 'refine and add a few new essential features' I added crisp chat and an easy way for current logged in users to get in contact. This was so important and it was great to feel more connected to my users I started receiving more helpful comments and questions which meant I could start to better prioritize what to work on. Also just by letting my users know I was there I started to build up better relationships with a few people who have now ended up going pro this month. My total revenue this month so far is just over $230 meaning I crossed the 1k mark. It feels great to have got here, but this has been no easy challenge at all. For anyone who's thinking about doing the saas thing and thinks they can start earning real bucks in a month or so... I would say this is most likely not going to be the case! But... I knew this would most likely be the case. I had built and successfully exited a few products before and now I'm playing the long game. My goal is that within 12 months from now I can stop freelancing and even If I only grow by 4 paid users a month I should nearly, just about be earning enough to pay the bills!! It's been a long old slog to get here (8 months in fact). Here's rough timeline of what the last 8 months have looked like: Month 1 - validation: My tool called Basefront - basefront.app is within the Airtable space (it's a tool to create directories, galleries and job boards with airtable data that you can integrate on any site) and I had already built up an audience in this space. In order to get validation before I actually went ahead and built the thing I set myself a goal of getting 10 presales at heavily discounted rate. I managed to get 12 presales before the initial MVP went live and this for me was enough validation to build. basefront.app At this point total revenue was around $450. Months 2-5 - build: Surprise, surprise, this actually took alot longer than the 1 month I initially planned, more like 3 months. There was just no way round it. Working with the airtable API and creating the customization features I had planned meant this was a hefty build and thats with stripping things back like user groups, paywalls etc etc. I built the tool in bubble using nocode but essentially I use it to then create the code my users then add to their stack. I used Claude (anthropic) alot for the code part of things - massive help. Month 6 - 'We're live in beta' My first email went out to my existing list and this was an exciting and nerve wracking time. My list wasn't massive so my plan was to essentially use this phase as beta testing. The tool has a free plan and I made it clear we were in beta. I also asked everyone who used the tool if they would be happy to provide feedback for 3 months of full access PRO plan. I managed to get some great feedback, but honestly it's painful, of 160 or so people on my list, about 30 tried it and 5 came back with helpful feedback and by the end of this month I also managed to get another 4 paid users signed up (who interestingly preferred to pay than to offer feedback in return for PRO access). Revenue at this point was close to $600. Month 7 - 'fix as much stuff as possible' There's always going to be things that slip through the net and bugs that popup. I knew if I could just get the product to a 'useable' and 'enjoyable' state that my users wouldn't mind about a few small bugs and fixes (especially as I made it clear I was in beta). I Built a simple logging process to track common user activity (creating, editing deleting etc) and this gave me valuable insight into any issues that were arising. I should have probably added something like hotjar for even better insight (this is on my list still). [It's worth noting that as soon my product was in beta I also did marketing every week day for at least 1 hr] So by this point I had done nearly 8 weeks of marketing and the compounding effects started to take place, I was getting on average 2 free users sign up a day (around 60 per month). I got another 5 pro users sign up this month a few on annual so my total revenue at this point was around $780. Month 8 - 'refine and add a few new essential features' I added crisp chat and an easy way for current logged in users to get in contact. This was so important and it was great to feel more connected to my users I started receiving more helpful comments and questions which meant I could start to better prioritize what to work on. Also just by letting my users know I was there I started to build up better relationships with a few people who have now ended up going pro this month. My total revenue this month so far is just over $230 meaning I crossed the 1k mark. It feels great to have got here, but this has been no easy challenge at all. For anyone who's thinking about doing the saas thing and thinks they can start earning real bucks in a month or so... I would say this is most likely not going to be the case! But... I knew this would most likely be the case. I had built and successfully exited a few products before and now I'm playing the long game. My goal is that within 12 months from now I can stop freelancing and even If I only grow by 4 paid users a month I should nearly, just about be earning enough to pay the bills!!

Crossing $1k Revenue for my App :)

The template below has consistently brought me success; it’s an outstanding method for organizing technical articles. Template Introduction
    Learning Objectives
    Prerequisites
    Getting Started
      Sub Topics 1
        Code Examples for Each Sub-Topic
        Output
      Sub Topics 2
        Code Examples for Each Sub-Topic
        Output
    Final Thoughts/Conclusion
    Github Sample (If Applicable)
    Impressum Here’s a List of Statistics That Demonstrate the Success of Following This Template: Tip 1: How to Write an Introduction Writing a compelling introduction is crucial for grabbing the reader’s attention and setting the base for the article's contents. Clearly define the topic of the article
Briefly explain why the topic is important
Define the problem you’re trying to solve
Set tone Tip 2: How to Write Learning Objectives Define what the reader is going to learn after finishing the story. Clearly define the skills the reader will gain
Don’t write what you aren’t delivering. Example Tip 3: How to Write Prerequisites Define what knowledge or skills are required to understand the article. Identify the Required Knowledge or Skills Example Tip 4: How to Write “Getting Started” The simplest trick is to divide the content into sub-topics and create a section for the same. Example Divide each section with a paragraph and code example for each of the sub-sections. Bonus: Add the output of the code as a screenshot or GIF if applicable. Tip 5: How to Write “Final Thoughts/Conclusion” Summarize key points.
Highlight the takeaways.
Provide CTA (Call to Action) if applicable. Tip 6: Github Sample This section can be optional, but if you add a GitHub sample, it enhances the article in many ways. It acts as a testament to the code examples above.
Enhance learning with practical examples.
Improve SEOs too.
Most Devs are searching on Google to solve a problem, and a GitHub sample makes their life easier. Tip 7: Add Impressum An Impressum provides more information about the author; it adds professionalism and credibility to the story. Keep it short and crisp.
Don’t add too many links.
Don’t ask for claps as the Medium doesn't encourage it. Medium Impressum Example C# Programming🚀 Thank you for being a part of the C# community! Before you leave: Follow us: Youtube | X | LinkedIn | Dev.to Visit our other platforms: GitHub Conclusion The above template has proven to be highly successful for writing technical articles, engaging readers, and providing a standard structure to the stories Including a GitHub sample further solves the challenges a dev faces while looking for practical implementations of the code. The structure makes the content more memorable & actionable. More Cheatsheets Cheat Sheets — .Net The template below has consistently brought me success; it’s an outstanding method for organizing technical articles. Template Introduction
    Learning Objectives
    Prerequisites
    Getting Started
      Sub Topics 1
        Code Examples for Each Sub-Topic
        Output
      Sub Topics 2
        Code Examples for Each Sub-Topic
        Output
    Final Thoughts/Conclusion
    Github Sample (If Applicable)
    Impressum Introduction
    Learning Objectives
    Prerequisites
    Getting Started
      Sub Topics 1
        Code Examples for Each Sub-Topic
        Output
      Sub Topics 2
        Code Examples for Each Sub-Topic
        Output
    Final Thoughts/Conclusion
    Github Sample (If Applicable)
    Impressum Here’s a List of Statistics That Demonstrate the Success of Following This Template: Tip 1: How to Write an Introduction Writing a compelling introduction is crucial for grabbing the reader’s attention and setting the base for the article's contents. Clearly define the topic of the article Briefly explain why the topic is important Define the problem you’re trying to solve Set tone Clearly define the topic of the article Briefly explain why the topic is important Define the problem you’re trying to solve Set tone Tip 2: How to Write Learning Objectives Define what the reader is going to learn after finishing the story. Clearly define the skills the reader will gain Don’t write what you aren’t delivering. Clearly define the skills the reader will gain Don’t write what you aren’t delivering. Example Example Tip 3: How to Write Prerequisites Define what knowledge or skills are required to understand the article. Identify the Required Knowledge or Skills Identify the Required Knowledge or Skills Example Example Tip 4: How to Write “Getting Started” The simplest trick is to divide the content into sub-topics and create a section for the same. Example Divide each section with a paragraph and code example for each of the sub-sections. Bonus: Add the output of the code as a screenshot or GIF if applicable. Bonus: Tip 5: How to Write “Final Thoughts/Conclusion” Summarize key points. Highlight the takeaways. Provide CTA (Call to Action) if applicable. Summarize key points. Highlight the takeaways. Provide CTA (Call to Action) if applicable. Tip 6: Github Sample This section can be optional, but if you add a GitHub sample, it enhances the article in many ways. It acts as a testament to the code examples above. Enhance learning with practical examples. Improve SEOs too. Most Devs are searching on Google to solve a problem, and a GitHub sample makes their life easier. It acts as a testament to the code examples above. Enhance learning with practical examples. Improve SEOs too. Most Devs are searching on Google to solve a problem, and a GitHub sample makes their life easier. Tip 7: Add Impressum An Impressum provides more information about the author; it adds professionalism and credibility to the story. Keep it short and crisp. Don’t add too many links. Don’t ask for claps as the Medium doesn't encourage it. Keep it short and crisp. Don’t add too many links. Don’t ask for claps as the Medium doesn't encourage it. Medium Impressum Example C# Programming🚀 Thank you for being a part of the C# community! Before you leave: Follow us: Youtube | X | LinkedIn | Dev.to Youtube X LinkedIn Dev.to Visit our other platforms: GitHub GitHub Conclusion The above template has proven to be highly successful for writing technical articles, engaging readers, and providing a standard structure to the stories Including a GitHub sample further solves the challenges a dev faces while looking for practical implementations of the code. The structure makes the content more memorable & actionable. More Cheatsheets Cheat Sheets — .Net Cheat Sheets — .Net

How to Unlock 50K Views on Medium With This Winning Article Template

Enhance Your UI/UX With These 16 Web Designer Resources🔥🎨

Stories, News & Mentions about CRISP

Crisp’s Stories on HackerNoon