Broken website, download links don't work

Community
1

I would like to use FoundationDB, but all the links on the download page are broken.

Further the main documentation website (FoundationDB 6.3 — FoundationDB 6.3) doesn’t let you scroll the navigation bar on the left, so it’s really difficult to browse information.

1 Like
2

@ammolitor, here’s the full list of broken downloads: --2021-12-09 00:04:45-- https://www.foundationdb.org/downloads/6.3.22/rhel6/ins - Pastebin.com

I ran:

wget -e robots=off --spider -r --page-requisites --convert-links -o run.log https://www.foundationdb.org/download/
grep -B2 404 run.log | grep downloads
1 Like
3

Does anybody know of an alternative location for the FoundationDB packages?

4

I needed them for an automated build process over the weekend, so I built it from scratch. I realize that’s not fun, but depending on how much of a hurry you’re in, perhaps it is an option.

I used the docker build container, and instructions from:

and built debs without any hassle. Just do it on a machine with “enough” virtual memory. I had compiler processes taking up 4GiB of RAM.

1 Like
5

What are you all typically downloading from the website? Is it packages (rpm, deb, tgz), or other files (the more specific answers the better)?

I am looking at better solutions for hosting the files (the website “code” is in a pretty sad state). My current idea is Github Release Assets.

6

I was fetching the client & server debs for 6.3.18. I believe I’ve seen other pipelines doing similar things.

When I noticed the site was down, I went to the Github releases and expected to see the rpms & debs from the website also attached there. I was surprised when they weren’t.

1 Like
7

Here’s how some information regarding both my personal and corporate usage of the website/releases.

I’m working on the Rust binding. CI is currently using the official deb package during GitHub Action’s setup, which means PR and scheduled correctness tests are stuck for now. This is something that might change in the future, as I would like to have some testcontainers to bootstrap on the fly multiple FDB version. For example, to add FDB-7.0‘s support, I have setup a scheduled GitHub actions to build every Sunday {deb, targz, docker, docs, Joshua} targets on release branches. I’m using it locally to test the binding. This means for now, I cannot run the CI in his current state to check this kind of work.

On my company’s side, we are waiting for the official 7.0 release to start directly with Redwood. We are building stuff from sources, so the website is not used. However, to test layers, we will most certainly use testcontainers, so we will pull the official Docker images. I’m using testcontainers here if you want to see how it looks.

Github release assets looks really nice indeed, with some DockerHub releases :rocket:

Feel free to ask any questions, and merry Christmas to everyone :christmas_tree:
-Pierre

8

I also download the client and server debs from foundationdb.org. Github release assets would be a perfect solution for my needs. To be specific:

https://www.foundationdb.org/downloads/6.3.15/ubuntu/installers/foundationdb-clients_6.3.15-1_amd64.deb

https://www.foundationdb.org/downloads/6.3.15/ubuntu/installers/foundationdb-server_6.3.15-1_amd64.deb

and

https://www.foundationdb.org/downloads/6.2.28/ubuntu/installers/foundationdb-clients_6.2.28-1_amd64.deb

(to support version migration)

9

The release assets are being added to GitHub now. Feel free to ping me if you need a file that is not included in the release assets. Here is a link to the latest 6.3.x release: Release Release 6.3.22 · apple/foundationdb · GitHub

10

Thanks @ammolitor! Everything is working on our side, we are now updating the related Github Action to setup FDB.

11

I used to pull windows installer from https://www.foundationdb.org/downloads/${Version}/windows/installers/foundationdb-${Version}-x64.msi, it looks like windows build is not part of Github release

12

Official Windows builds stopped after version 6.3.10.

13

@ ananthakumaran Here is how i manged to build for windows versions 6.3.23 and 7.0.0 (thanks to @moulmahdi). You need a windows docker host with container mode set to windows and hyperv enabled.

###############################
# BUILD 7.0.0
###############################

docker run -ti doxense/foundationdb-windows-build:latest
git clone --depth 1 --branch 7.0.0 https://github.com/apple/foundationdb.git
md fdbbuild
cmake -G "Visual Studio 16 2019" -DFDB_RELEASE=ON -DDISABLE_TLS=ON -A x64 -T"ClangCL" -S C:\foundationdb -B C:\fdbbuild --debug-trycompile
cd fdbbuild
msbuild /p:CL_MPCount=1 /m /p:UseMultiToolTask=true /p:Configuration=Release foundationdb.sln


###############################
# BUILD 6.3.23
###############################

docker run -ti doxense/foundationdb-windows-build:latest
git clone --depth 1 --branch 6.3.23 https://github.com/apple/foundationdb.git
chocolatey install openssl micro
micro foundationdb/cmake/FDBComponents.cmake
# now edit file to reflect change below the steps, until they integrate this pull request
refreshenv
md fdbbuild
cmake -G "Visual Studio 16 2019" -DFDB_RELEASE=ON -A x64 -T"ClangCL" -S C:\foundationdb -B C:\fdbbuild
cd fdbbuild
msbuild /p:CL_MPCount=1 /m /p:UseMultiToolTask=true /p:Configuration=Release foundationdb.sln

###
# edit in micro:
##

remove if(WIN32) ... endif() brach in the file and add this below set(OPENSSL_USE_STATIC_LIBS TRUE) instead:

else()
  set(OPENSSL_USE_STATIC_LIBS TRUE)
  +if(WIN32)
  +  set(OPENSSL_MSVC_STATIC_RT ON)
  +endif()
  find_package(OpenSSL)
1 Like