File uploads automagically appear in /static/uploads/action/id. Using the local filesystem is a bit dated, we should offer configurable cloud storage options where people could choose provider (e.g. Azure or AWS) and enter their own access key to their own blob storage account.

(also, uploads currently keep the original file as picture.upload wasting space. Keeping this file should at least be

Documentation

The presentations used to be swipable horizontally but we recently enhanced this. We are going to introduce the ability to swipe vertically and also developed a new mode we called papyrus which basically transform a presentation into a "landing page".

These options can be set on the deckgo-deck main component with the properties direction and `directionM

fetchPypi just calls fetchurl underneath but has a slightly different calling syntax in order to construct the URL. It would be great to track these external dependencies using niv. :-)

Currently, we are not able to
a) symbolically execute init code with symbolic arguments
b) get srcmapping for init code with arguments

We could change ContractCode as follows:

data ContractCode
  = InitCode (ByteString, Buffer)    -- ^ "Constructor" code, during contract creation (possibly with arguments)
  | RuntimeCode ByteString           -- ^ "Instance" code, after contract crea

Otherwise one might get an error like:

cachix push /nix/store/7i1kqf6x52l1fhqqdmqgggjr0zigggik-cachix-0.1.3/bin/cachix

NoInput "You need to specify store paths either as stdin or as a cli argument"

It would be nice to have an easy way of installing bash completions from optparse-applicative.

We've added a small post install script to our own CLI tools with a module like the following:

{pkgs, ...}:
{
    packages.our-pkg-one.components.exes.our-exe-one.build-tools = [ pkgs.installShellFiles ];
    packages.our-pkg-one.components.all.postInstall = pkgs.lib.mkForce "";
    pac