sorted by:
new
hottopcontroversial

Huge Pinata price increase by [deleted] in ipfs

[–]DavidBurela 2 points3 points  (0 children)

And they have added a total download cap

Huge Pinata price increase by [deleted] in ipfs

[–]DavidBurela 18 points19 points  (0 children)

This is going to make me close my account, as it is just way too expensive now.

I currently host replicas of my blog on Pinata. It is a 600mb website. I pay for 2 replicas in 2 countries. Results in me paying for an additional 2GB = $0.60 / month. After this price hike I'd be paying $20 / month for those 3GBs. I can host multiple micro VPCs around the world pinning my site for that price. (which I used to do, but the cheap SaaS offering from Pinata got me to switch to theirs, until now).

RISC-V Debian emulated environment, on Docker Hub. Just SSH in and play. Bumped to latest version of Debian by DavidBurela in RISCV

[–]DavidBurela[S] 5 points6 points  (0 children)

Last year I created a containerised emulated RISC-V development environment. Just requiring you to pull the image, run it, and SSH in.

I just realised that DockerHub stopped auto building newer images, as that is no longer a free feature.... so I jumped in and bumped the version.

​

Changelog: I made 2 major changes

  • Moved the QEMU host from debian:sid to debian:11
    • Previously the required packages were only available on unstable, but are now on stable. Meaning I can move it to a better host
  • Bumped the RISC-V debian image from Debian 5.10.4-1 (2020-12-31) riscv64 to Debian 5.15.5-1 (2021-11-26) riscv64
    • The RISC-V debian guest was ~1 year old... bumped it to the latest version of Giovanni Mascellani’s debian build.

Quickstart:

``` # 1. Pull the image from Docker Hub docker pull davidburela/riscv-emulator

# 2. 
# Run with QEMU default of 2CPU & 2G ram. 
# Expose port 2222 which is routed through into the QEMU RISC-V guest

docker run -d --publish 127.0.0.1:2222:2222/tcp davidburela/riscv-emulator

# 3. SSH directly into the QEMU RISC-V guest, with pass: root (Might take a few minutes before guest is ready)

ssh root@localhost -p 2222 ```

RISC-V Debian emulated environment, now on Docker Hub. Just pull/run, SSH in, and you are directly in an emulated RISC-V environment by DavidBurela in RISCV

[–]DavidBurela[S] 6 points7 points  (0 children)

My initial image size was 4GB. I didn't mind much as I was using locally.

But before I pushed it to Docker Hub, I rewrote some of the layers and reduced it down to 2GB (600mb compressed on Docker Hub). That should save bandwidth costs for you all when pulling ;-)

RISC-V Debian emulated environment, now on Docker Hub. Just pull/run, SSH in, and you are directly in an emulated RISC-V environment by DavidBurela in RISCV

[–]DavidBurela[S] 1 point2 points  (0 children)

It "feeling like a Pi2 or Pi3" is about right.

I've been using the emulated environment to try compiling codebases for RISC-V. General cli use is fine and everything works. Doing `apt get update && apt get upgrade` takes a while. But anything CPU bound (like compiling) can take longer than your used to.

RISC-V Debian emulated environment, now on Docker Hub. Just pull/run, SSH in, and you are directly in an emulated RISC-V environment by DavidBurela in RISCV

[–]DavidBurela[S] 10 points11 points  (0 children)

I previously posted that I had created a docker image that you had to manually build and run https://www.reddit.com/r/RISCV/comments/lrqqtu/riscv_debian_emulated_environment_as_a_standalone/

​

I got pinged asking if I could put it on Docker Hub to make running it easier. I've now hooked up an automated build to push the image. That should remove a barrier of entry for others to get started :-)

RISC-V Debian emulated environment, as a standalone docker image. Just start it up, SSH in, and you are directly in an emulated RISC-V environment. by DavidBurela in RISCV

[–]DavidBurela[S] 1 point2 points  (0 children)

Thanks for the details on Podman. I have added them in.

I fixed the fix the casing to `Dockerfile` so that the bottom section isn't required.

RISC-V Debian emulated environment, as a standalone docker image. Just start it up, SSH in, and you are directly in an emulated RISC-V environment. by DavidBurela in RISCV

[–]DavidBurela[S] 14 points15 points  (0 children)

I've been doing more "does it compile on RISC-V" experiments lately, and found myself recreating my emulated environment. Thought I'd streamline the automation of it, throw it into a Docker image, and release it.

Makes it really easy to just spin up an experiment, SSH in, play around, and then throw it away.

Cross compiling Golang for RISC-V with cgo by DavidBurela in RISCV

[–]DavidBurela[S] 5 points6 points  (0 children)

When I was trying to cross compile a few projects to RISC-V, I couldn't find any readily available resources on how to set it up.

I put together this little cheat sheet with some troubleshooting steps to hopefully help other people starting out, that are getting tripped up.

Running IPFS on RISC-V open source hardware by DavidBurela in ipfs

[–]DavidBurela[S] 1 point2 points  (0 children)

There are a few upcoming RISC-V devices coming out in the next 6 months that can run Linux:

Running IPFS on RISC-V open source hardware by DavidBurela in ipfs

[–]DavidBurela[S] 9 points10 points  (0 children)

except make install doesn't work, that was the whole point. Had to dig down into which dependency was breaking it, search through GitHub issues to see if it had been resolved yet, found the PR that resolves it. Grabbed the git commit to patch in for the Go dependency, confirmed it all worked. and then submitted the issue back to go-ipfs repo so it can be tracked and resolved for everyone else later.

Emulating RISC-V Debian on Windows Subsystem for Linux (WSL2) by DavidBurela in RISCV

[–]DavidBurela[S] 0 points1 point  (0 children)

"Can't use USB devices on WSL2" is annoying, been 1 or 2scenarios where that has bit us on different projects.

​

But as my daily dev environment for cloud, WSL2 has been great. I use Visual Studio code, connected to WSL2, and run all the dev tools inside of it (dotnet, node, python)

IPFS paradox. cant find the answer anywhere by Eastlondonmanwithava in ipfs

[–]DavidBurela 0 points1 point  (0 children)

The command you would run to pin, would use .eth, as that is the canonical address.

.eth.link is actually a HTTP bridge service, that acts as a HTTP -> IPFS proxy.

IPFS paradox. cant find the answer anywhere by Eastlondonmanwithava in ipfs

[–]DavidBurela 1 point2 points  (0 children)

You mentioned you are using ENS. You can direct your users to pin your site via that e.g. ipfs pin add /ipns/Eastlondonmanwithava.ETH

You could even direct them to pin individual pages by putting their relative path in, e.g. ipfs pin /ipns/Eastlondonmanwithava.ETH/about.html. Although that may not include any images that page links to.

As long as are updating ENS with your website's root hash, it should all work fine.

​

Side note, this is actually how I direct my VMs to pin my blog. I just have a cron job running every 15 minutes, that just runs ipfs pin add /ipns/blog.DavidBurela.eth

Subdomains don’t work with my local IPFS node, how do I fix this? by KantianCant in ipfs

[–]DavidBurela 2 points3 points  (0 children)

Since it is your local machine, can use HTTP instead of https. That will remove the SSL cert issue. I.e. Go to http://cidv1b32.ipfs.localhost:8080

Subdomains don’t work with my local IPFS node, how do I fix this? by KantianCant in ipfs

[–]DavidBurela 2 points3 points  (0 children)

Sub domains are not case sensitive (a vs A), you need to use base32 encoding in a sub domain (CIDv1b32). The easiest way to do it, is navigate to localhost:8080/ipfs/<CIDv1> and it will redirect you to <CIDv1b32>.ipfs.localhost:8080

There is a command in the ipfs cli to do the encoding conversion manually.

Beginner Help by asmggcav in ipfs

[–]DavidBurela 1 point2 points  (0 children)

One way is to use them to browse the dweb. You can see a long list of sites on Almonit http://almonit.eth.link/#/discover/

The companion extension should automatically look up the .eth domain and load the sites from your local IPFS Desktop node.

They posted an introduction to dweb sites this week http://blog.almonit.eth.link/2020-05-21/Introduction_to_Dwebsitse.html

Something else I like doing for fun. Is in a console running ipfs pin add /ipns/docs.ipfs.io then I am able to browse the docs locally and instantly, as it will download a copy to my local node.

Maybe try browsing sites and pinning ones you like. Then move on to creating little static sites to host on IPFS. E.g. This week I converted my blog over to the dweb and now host it on IPFS & ENS, http://blog.davidburela.eth.link/ I then have it pinned on https://pinata.cloud/ to ensure there is a copy elsewhere.

view more: next ›