Changelog

What’s up, Fleek Freaks?

We’re back again with new, exciting updates to the Fleek platform that we’ve been working on for the past few weeks. Today, we’re highlighting a few new things: Fleek Functions UI to create and deploy Fleek Functions, improvements to the deployments page, updates for our migration from .co to .xyz, and the start of support for multiple Git providers. ⚡

You can try out all the new features for yourself directly in the Fleek app. Let’s dive into what the team has been working on in August:

---

Email invitations

Fleek users can now invite others to their projects via email addresses with any permission deemed fit by the user sending out an invitation.

With our new transactional email feature shipped, the invited user gets an email with a CTA button they can click on to be redirected back to their Fleek dashboard.

---

Fleek Functions UI

Previously, Fleek Functions were accessible only via the Fleek CLI. That’s changed with this new release as you can now create, manage, and customize Fleek Functions directly from the Fleek app UI!

Fleek Functions are onchain serverless edge functions powered by Fleek Network. If you’re unfamiliar with Fleek Functions, you can learn more here. The team is super pumped to see all the cool things developers are testing since the alpha CLI release.

Deploying your first Fleek Function just got a lot easier 🤙

---

Deployment page improvements

• We no longer calculate the total build duration including queued time— true build times should now be more accurate

• Preview URLs for deployments are now available

• Queued deployments can now be canceled if necessary

• Commit messages will now be displayed without a delay and on a more timely basis

• The redeploy button is no longer disabled if there is an ongoing deployment, allowing for queued deployments

---

Changelog page

We now have a dedicated changelog page! Previously, changelogs and release notes lived in our blogs and guides sections on the Fleek website. With this latest release, we now have one page to list all of the exciting improvements made by the team, in chronological order. You can go to fleek.xyz/changelog to check out the new page 🤙

---

Git provider management

Deployment Git integrations with GitHub can now be managed from within your account’s Settings page. This allows you to configure the GitHub apps necessary for managing deployments in your GitHub repositories from within the app.

You can now:

• See the statuses of the Fleek CI App
• Check which repositories have permission
• See which needs to be installed

---

Other fixes and improvements

• New customer support feedback experience from within the app for in-app users.

• The Git integration flow that allows the re-installation of a new GitHub app no longer affects existing sites

• Transactional emails for synchronized updates on activities on user’s accounts

• Fleek CLI version 2.9.0: Amends and enhancement to bundling parameters, among other things.

Upcoming features:

• Public IPFS gateway

• Backend rewrite to Rust

---

Coming soon: Migration from Fleek.co to Fleek.xyz

In the interest of providing the smoothest possible transition period from Fleek.co to Fleek.xyz for our users, we have put in a lot of effort into testing to ensure that our infrastructure internally migrated successfully before opening up the floodgates to user projects.

With the migration, users will see:

• Improved UX
• Access to many of the new features the team has been shipping to enable seamless Fleek integration across your stack.
• Improved user support
• Access to a ton of resources for users and teams to better utilize Fleek’s tools, including templates, boilerplates, guides, and more.

Stay tuned for more details on the migration process, as well as the release of the migration assistance tools, soon.

---

That’s all for this changelog!

You can see a list of all changes made to the app on the new Changelog page on Fleek.xyz.

Don’t forget to:

• Follow us on X
• Join our Discord server
• Catch up on all our guides and resources

And stay up to date with that the team is cookin’!

We’re back with a new update to the Fleek platform, this time packed with new features and enhancements rolled out throughout February, aiming to streamline your development process and improve the security of all projects deployed on Fleek for end users.

In this recap, we’ll cover the new phishing protection mechanisms, refined application credentials management, and improved image handling improvements that were rolled out to the Fleek platform last month ⚡

Or, you can just try all the new features yourself on Fleek which is now in Open Beta– anyone can now create an account and start trying the new platform, no whitelist required 🤙

Let’s get into what the devs were cookin’ throughout February:

---

Phishing Protection: Automatic Phishing Detection

The main focus for the dev team this month was the implementation of a new process to identify potential phishing sites among all websites deployed and hosted on Fleek. This system mirrors the one already in place on Fleek.co, where each website undergoes a phishing analysis in the deployment process. This mechanism aims to protect the product and the service we provide from malicious actors and ensure all end-users enjoy a better experience using sites deployed on Fleek.

Sites flagged for phishing are automatically removed, alongside the associated user account and all related resources. In cases where a site’s status is ambiguous, we conduct a manual review and maintain a list for such instances internally. In the manual review process, we work with a group of trustee sources to whom we delegate the review to determine if the site is phishing.

Anyone flagged for deploying a phishing site on Fleek will find themselves on a blocklist to prevent individuals associated with phishing activities from registering or signing into the platform in the future. Users who believe their site was mistakenly flagged can reach out to our Support team for assistance and manual review.

To track the success of all of our new phishing protection efforts, we’ve added a few new metrics to our tracking system. This now includes the number of phishing sites:

• Automatically detected
• Manually detected
• Deleted for phishing (manually and automatically)

As well as the penetration rate, or the ratio of manually deleted sites against the total sites that make it through the automatic phishing detection. This data-driven approach enables us to continually refine our detection strategies, ensuring Fleek remains a secure platform for both developers and users of sites deployed on Fleek.

Alongside the new automatic phishing detection tools, we’ve also added an edge rule to all pullzones on Fleek restricting access to just its custom domain. This will reduce potential phishing entry points, as sites with pullzones can no longer be accessed via the pullzone URL (i.e. fleekcdn.xyz).

Our goal with this update is to proactively eliminate both the deployment of phishing sites and the users who create them on Fleek. We’ll keep you updated on the success of the new phishing detection efforts in future changelogs 🤙

---

Application Credentials

We’ve also now added the ability to create application credentials directly within the Fleek UI.

Anyone can now interact with the SDK directly from a client in a secure way, through whitelisted domains, allowing only those with the application credentials to access the specified domains. Creating and managing Application Credentials can be done in the Application Credentials tab within the settings of your Fleek project:

---

Image Improvements

We’ve made several improvements to how images are handled on the platform in this update as well. All images should now have overall improved quality and reliability:

• Default avatars are now assigned on account creation.
• Custom avatars are now cached immediately
• Template image previews have been fixed, resolving the issue of constant loading.

---

Bug Fixes and Improvements

Also included in this release:

• Delete flows for sites and projects are now simplified.
• Removed unnecessary dot displayed on delete modal.
• Enhanced deployment pipeline reducing cases where the deployment got stuck.
• New flow for self-managed deployment on the UI.
• Username is now pre-filled on account creation.
• ENS configuration modal now comes with the exact record to paste into the content hash.
• ENS validation now takes into consideration the IPFS:// and IPNS:// prefixes.
• Environment variable names can be created with up to 150 characters
• Fixed bug where modal was not appearing after creating a domain for a PGW
• ENS modal now displays the content hash in smaller screen resolutions.

For more details on all the new features, bug fixes, and improvements made in this release, check out our docs!

---

That’s a wrap for February, folks!

The team has been heads down rolling out new improvements to make the Fleek experience smoother and more secure for all end-users, as well as some behind-the-scenes work on cool new features to debut soon.

Got feedback or need some help navigating the new updates? Chat with the team and join the conversation in our Discord community. Also, follow along with all the new updates coming to the Fleek platform on X!

See you in the next changelog Fleek Freaks ⚡

What’s up Fleek Freaks?

We’re back with an update to the Fleek.xyz Alpha! This jam-packed v.0.0.4 update brings us to near-feature parity with the Fleek.co platform, an important goal for the team as we approach the start of the Fleek.co to Fleek.xyz migration.

If you haven’t been added to the closed alpha yet and you want to try any of the new features we’re rolling out with this release, fill out this Typeform and we’ll get you onboarded!

Let’s get into everything coming with v0.0.4, starting with ENS:

---

ENS Integration

A major step in the direction towards the sunsetting of Fleek.co is reaching feature parity with the Fleek.co platform. With v0.0.4, we’re excited to reintroduce a familiar feature for our long-standing users from Fleek.co – the ability to directly configure ENS records within Fleek.

An improvement on the Fleek.co iteration that users are familiar with, this version allows users to set the content hash for their domains without leaving the Fleek platform, as well as now handle subnames and name unwrapping in-app. It’s quick, easy, and allows you to use your ENS domains for any of your builds on Fleek:

Deployment Details Page

The v0.0.4 update also comes with a little upgrade to the deployment details page! Now, you will see a more detailed overview of each step in the deployment process. The new page shows progress and failures for each step, with copy-to-clipboard details, making deployments more transparent and support a little more streamlined.

File Upload Size Limit Increase

Thanks to some improvements to our build creation handling and storage upload processes, we’ve been able to double the maximum file upload size. Users can now upload files up to 2GB in size (previously 1GB maximum) 🤙

Wallet Linking

Now, users can effortlessly link their wallets to their Fleek accounts, enabling a range of features like secure logins, access to the new ENS features, and more wallet-exclusive features in the future.

If you didn’t sign up for the Fleek.xyz alpha with a wallet, linking yours is super easy. Just navigate to your Account Settings, and Log-In Connections to connect any supported wallet to start trying the wallet-exclusive features on Fleek.xyz.

Oh, and with v0.0.4, we’ve added the ability to do it the other way around too! If you signed up with a wallet address, you can now link your email address to your profile in your Account Settings.

---

Other Fixes and Improvements

Along with the above, the devs did their usual bug squashing and fixes including:

• Changed the way we create pins so we display them immediately in the UI after the upload is complete.
• Increased the docker image name character size to 50 characters and the env variable value character size to 250 characters.
• Improved the efficacy of the site screenshot generation.
• Site slug now has a maximum of 63 characters long.
• Fixed a problem where the site slug was not clickable after the first deployment.
• Project name can be changed on Arc Browsers.

You can see a full list of changes included in the v0.0.4 release of the Fleek.xyz alpha in our docs!

---

And that’s what’s changed in this v0.0.4 update of the Fleek.xyz alpha. We’re pumped to be back this year rolling out updates to the new platform– we can’t wait for you to see what we have cookin’ up 🤙

We have more updates coming to the new Fleek.xyz platform in the near future, including community-submitted templates. Stay tuned ⚡

Follow along with all of the coming releases on X and join the community of testers in our Discord server.

If you want to try any of the new features we’re debuting with this update and you aren’t a part of the alpha yet, fill out this Typeform and we’ll get you onboarded.

See you soon for the next update!

It’s been about two weeks, meaning it’s time for another bi-weekly update to the Fleek.xyz Alpha 🤙

The highlight for this release: Project, Site, and Gateway delete functionality! We’ve also done our usual bi-weekly bug-squashing to clean up your experience and fix a few minor issues.

Did you see the performance data from Fleek Network Testnet Phase {1}? Last week, the Foundation released the results from the successful Phase {1} performance testing period. Dive into the full performance analysis here!

Let’s get into the changes coming to the Fleek.xyz alpha with v0.0.3:

---

Delete Options: Projects, Sites, Gateways

A heavily requested feature is here– quickly and easily delete any Project, Site, or Gateway directly in the Fleek.xyz UI. When deleting any of the above, the user must go through a few confirmations to verify the removal of things like Domains, IPNS records, or anything else associated with the project.

IMPORTANT: Deleting a Project, Site, or Gateway is not reversible! Make sure you understand all warnings before progressing.

Project Delete

To delete a Project, head to the project dashboard, where you’ll need to acknowledge that deleting your project means the removal of the project’s:

• Sites
• Domains linked to the sites
• IPNS keys linked to the site
• Private Gateways
• Domains linked to Private Gateways
• Files Stored

Site Delete

When deleting a site, go to the site overview and click the Delete Site option on the general settings page. Deleting your site means the removal of all associated resources and means content for that site will no longer be served, including the domains and IPNS record linked to it.

Gateway Delete

For Private Gateways, you’ll be prompted to remove the gateway and all domains associated with it:

Other Fixes and Improvements

Alongside the new delete options, we’ve also added a ton of quality-of-life improvements and other fixes to the platform with v0.0.3 including:

• Now correctly handle the canceling state for deployments
• Now mapping the error when the git repository fails to be cloned correctly
• Added a new dropdown to select the type of storage for the project
• Files with special characters in the name are now rendering correctly on private gateways
• Fixed an error where users were stuck in the UI and unable to log in
• Added a button to add an organization to the verified GitHub account in the GitHub account selector

---

That’s all for this week! This is a smaller QoL update to bring a heavily requested feature and clean up a little behind the scenes as we prepare for the next major feature addition– Template Submissions ⚡

Follow along with the release of the Fleek.xyz platform on X and join the community of testers in our Discord server!

See you again in about two weeks for the next update 🤙

It’s that time again! We’re back for another bi-weekly update to the Fleek.xyz Alpha– this time with a new template option, faster file uploads, a few new features, and fixes.

Application form for the next batch of testers, who will get onboarded with v0.0.3 coming in ~2 weeks, is open here!

Let’s get into the changes coming to the Fleek.xyz alpha with v0.0.2:

---

Primary Domains

In an effort to simplify domain management, we’re introducing a new “Primary Domains” feature. The platform will now automatically reference your chosen primary domain for tasks related to sites or gateways. When you set up your first active domain, it becomes the default primary. As you add more domains, you have the flexibility to set a new one that your site defaults to.

If you decide to switch things up and remove your primary domain, you’ll get a prompt to set up a new one from your list of domains.

---

Lens Template

Head over to the templates page to try our new Lens template! Spin up your own fully functioning Lens social app in minutes with an easy-to-configure and customized template. Start with a timeline, as well as post and user search, and build from there.

You can access the new template here- give us a tag on X with your finished Lens build ⚡

---

Upload Improvements

You may have noticed uploads on the platform feel faster over the last week– that’s because we did a little refactoring on the backend and gave upload speeds a pretty significant boost! Files of all sizes upload ~10 times faster than before on the UI 🤙

---

Other Fixes and Improvements

As always, we’ve squashed a ton of bugs and added a few small improvements with this release!

• Increased memory in our deploy lambda to accommodate bigger site repositories
• Fixed a bug where the IPNS values were not being updated after a deployment
• Fixed a bug where the GitHub listener was not catching all the commits for deployments
• Improved error handling when the user is not using the default Fleek configuration files while deploying with GitHub Actions
• Created a canary project to monitor site deployment flow for better customer support and availability
• Fixed an error where we were showing the incorrect message when a site name was not available
• Fixed an issue with some users getting stuck in the welcoming screen
• Added an auto-generated domain on the site overview if there is no domain set
• Fixed a bug where the view site button on the recent deployment cards was not working

---

That’s all we have to share for v0.0.2! We’ll be back in about 2 weeks with another set of improvements, along with the next batch of alpha testers ⚡

Follow along with the release of the Fleek.xyz platform on X and join the community of testers in our Discord server!

See you in a few weeks 🤙

We’re back with another Alpha update, this time with a focus on laying down the foundation for an even more reliable platform and some new incoming features. Plus, if you’ve been hanging out on our alpha waitlist, we’ve got some good news: you’ll be approved tomorrow– keep an eye on your email for onboarding instructions!

If this is the first you’re hearing of the alpha, don’t worry our application form is still open, and we’ll approve the next batch of users with the next release.

Let’s get into the changes coming to the Fleek.xyz alpha with v0.0.1:

---

New Feature

Custom URL Slugs

The randomly generated on-fleek.app URL slugs will default to a combination of words but now, if you want something a little more personalized, you can change it to whatever available slug you want:

---

Fixes & Improvements

Validations

We’ve given our validation system a little tune-up in this update– now you’ll get a heads-up if the username or domain you’re entering has already been claimed or is in use in a previous project, as well as alerts on storage limits and other key notifications.

Other Improvements

• Added Trigger Deploy button in site detail
• Fixed SDK next.js installation issues
• Fixed an issue where CLI Users were unable to create a project
• Fixed site previews for pull requests
• Added option to cancel deployment that is already in progress
• Copy Filecoin Deal ID now copies the correct value
• Fixed bug where all the branches were not listed in the deployment process
• Now tracking how many times each template has been used
• Added new AR token balance monitors
• Streamlined support process now no longer needs users to provide details on things like Private Gateways, Project Members, Filecoin & Arweave file info, and other project/site details, when reaching out for support

That’s not all though– head here for a full list of the 50+ other changes and improvements coming to the Fleek.xyz Alpha with this release.

---

Coming Next

• Template Creation Flow: Instead of our initially planned submission process, users will be able to make a site template from any previously deployed Fleek site.
• Delete Options: Adding options to better manage sites and projects, like account, project, and site deletion.

---

That’s all for this update! See you all in ~2 weeks for the next batch of improvements coming to the Fleek.xyz alpha 🤙

Remember: if you applied to become an alpha tester since our last release notes, check your email for onboarding instructions coming in the next day. If you haven’t applied– the form is still open!

Follow along with the release of the Fleek.xyz platform on X and join the community of testers in our Discord server!

See you soon ⚡

---

Useful links ⚡

• Alpha submissions for Fleek are still open
• Read our documentation in full
• Bookmark the changelog so you don’t miss a single thing

What’s up Fleek Freaks? We’re back with another Fleek Release Notes, giving y’all a look into the improvements and bug fixes we’ve implemented into the Fleek.xyz alpha over the last week. If you missed the previous Fleek Release Notes, get caught up here!

This week, the focus was mainly on some bug fixes, visual improvements, and foundational work for upcoming features like site deletion/template submission. Don’t forget: if you want to take part in the Fleek.xyz alpha, join our discord server and fill out the application so you can join in the testing ⚡

Let’s dive into the updates, shall we?

---

New Features

UI & Experience:

We heard your feedback and have spent the week making dark mode the default, with some other improvements sprinkled in:

1. Dark Mode is now set as the Default UI Theme:

2. Template pages now render the repository’s Readmes as the description

---

Fixes

UI & Experience:

This week, the frontend team worked on fixing several bugs from the interface, which include:

• Fixed site breadcrumbs to remove 304 redirect errors while navigating
• The flow to accept an invite without having a Fleek account has been now implemented
• When logged out and visiting the templates page, if the user logins it now redirects them this section after doing so
• Added 150-character-max to Environment variables in sites
• Removed the redeploy option from self-managed deployment sites
• Fixed Go to Docs button typo after CLI login
• Improved image caching and loading across the app
• Fixed issue with Fleek logo glitching on Templates pages
• Added extra information in the gateway for users to understand how to access their files
• Added a 1GB per file/folder maximum size validation in storage UI
• Fixed issue where a project’s GitHub app configurations persisted even when changing projects

---

Inner-workings

While on the UI/user-facing front our updates end with the above, we have also been setting foundational work and improvements to the inner workings of Fleek.xyz, which prepare the platform for a couple of future releases:

• The base for the site and project deletion features have been set, and integrations can begin next.
• As well as the flow for community template submissions, with build settings validation, in preparation for integration of the feature to the frontend.

---

Coming Next Release

• Template submissions: Opening template submissions to the community
• Site and project deletion
• Trackers for how many sites have been created for each template
• Adding custom build command and publish directory to templates
• Fixing Site previews

---

That’s all for this time! Just a small update to smooth out a few issues spotted by our first groups of testers. We’ll be back with Fleek Release Notes 03 after another week in the lab 🤙

Follow along with the release of the Fleek.xyz platform on X and join the community of testers in our Discord server!

See you soon ⚡

---

Useful links ⚡

• Alpha submissions for Fleek are still open
• Read our documentation in full
• Bookmark the changelog so you don’t miss a single thing

Hey there Fleek Freaks! The Fleek Alpha is here and new testers are being onboarded every day if you haven’t gotten access yet to the Alpha, what in Vitalik’s name are you waiting for?

With the release of the alpha, setting the foundations for the release of V1, we’re bringing back our frequent release notes updates at a constant cadence under a new name: Fleek Release Notes 📔

What can you expect from the release notes? We’ll be releasing our nitty-gritty changes in our documentation, and with each we’ll post a Fleek Release Notes that does a double-click on the highlights and links to how to start using things. We’ll cover:

• New Features
• Important Bug Fixes
• Enhancements
• Any other team updates.

Today, given it’s the initial release, we’ll cover the Alpha’s base features - expect the next one to cover the fixes and enhancements we found in testing this week!

So, without further ado, let’s get into it ⚡

---

New Features

Projects

In the new Fleek, we have introduced Projects, a way to organize your sites, files, and else. This alpha release allows you to:

• Create a new project
• Invite other users to your projects

Sites

In this initial release, users can deploy/host apps via a managed deployment CI/CD in the app, or opt for the the CLI-based deployments(a.k.a. Self-Managed and built deployments). Users can:

• Deploy sites to IPFS storage by connecting their GitHub account
• Create sites to manage via the CLI
• Deploy sites from templates created by the Fleek team and the community
• Configure a custom domain on their sites via the UI
• Configure ENS domains on their sites via the UI
• Configure environment variables on their sites via the UI
• Configure build settings and deploy context for their sites

Storage

The alpha release introduces the revamped decentralized storage feature, with file pinning, with Arweave/Filecoin storage options and general IPFS addressability for all files. Users are able to:

• Store files in their projects using IPFS, Filecoin and Arweave
• See the file’s IPFS/Arweave hash, or its Filecoin deal ID (reminder: we use IPFS as the content addressing layer, no matter where the file is stored).

Settings

In the alpha we also introduced several settings pages where you can test more advanced features, such as private gateways. Users are able to:

• Set up avatars for their accounts, sites and projects.
• Configure via the UI private IPFS gateways to serve their content through them
• Configure a custom domain on their private gateways to serve their content through them

---

CLI/SDK version 0.7.0

Our CLI & SDK packages have been updated to v0.7.0 as well. [both have improvements described here]

You can find the CLI release here, and the SDK release here.

And this closes the first update from our team going into our closed Alpha. Expect all features from above to be expanded as we collect feedback and build around it.

---

Useful Links

• Get a seat to test the alpha of Fleek
• Read our documentation in full
• Check out that sweet new homepage

See you soon! ⚡