Currently people running PyWebServer 1.4.0 or Amethyst beta 0001 to 0038 cannot just upgrade to the latest release (Amethyst-b0039+) without some extra help. In here I plan to track what issues arise from migration and how to solve them.
Currently people running PyWebServer 1.4.0 or Amethyst beta 0001 to 0038 cannot just upgrade to the latest release (Amethyst-b0039+) without some extra help. In here I plan to track what issues arise from migration and how to solve them.
Due to the extreme configuration overhaul, the configuration is the main key of focus here, if unexpected behaviour that a user might have based their logic around has been fixed in the latest version, I will try to find a way to make stuff still work, but it is significantly lower priority compared to configuration issues.
Due to the extreme configuration overhaul, the configuration is the main key of focus here, if unexpected behaviour that a user might have based their logic around has been fixed in the latest version, I will try to find a way to make stuff still work, but it is significantly lower priority compared to configuration issues.
pywebsrv.conf is completely gone. Now only amethyst.conf exists. Most functions using the old config file will still work if they are put in the globals tag.
`pywebsrv.conf` is completely gone. Now only `amethyst.conf` exists. Most functions using the old config file will still work if they are put in the `globals` tag.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Currently people running PyWebServer 1.4.0 or Amethyst beta 0001 to 0038 cannot just upgrade to the latest release (Amethyst-b0039+) without some extra help. In here I plan to track what issues arise from migration and how to solve them.
Due to the extreme configuration overhaul, the configuration is the main key of focus here, if unexpected behaviour that a user might have based their logic around has been fixed in the latest version, I will try to find a way to make stuff still work, but it is significantly lower priority compared to configuration issues.
One note is that
pywebsrv.conf(the old configuration file) is still used for some queries, this will later be removed, don't base any logic on it!pywebsrv.confis completely gone. Now onlyamethyst.confexists. Most functions using the old config file will still work if they are put in theglobalstag.