Search Engine Project for EECS 398 W19 at the University of Michigan
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
Graham Eger ae15fbaf66 Update 'README.md' 12 months ago
.vscode push graham 4 years ago
doc merge 4 years ago
include combine anchor_words and links 3 years ago
spike updates 4 years ago
src combine anchor_words and links 3 years ago
test merge 3 years ago
.astylerc folder setup 4 years ago
.dockerignore apply 4 years ago
.gitattributes add .gitattributes 4 years ago
.gitignore merge 3 years ago
Makefile merge 3 years ago
Popular_nouns.txt Ranking files for Dennis in sorted order 3 years ago
README.md Update 'README.md' 12 months ago
TheCtles.png interface 3 years ago
alexa_index_sort.txt Sorted list of domain names to binary search through. 3 years ago
index.html interface 3 years ago
main pQueue map changes 3 years ago
results.css interface 3 years ago
results.html interface 3 years ago
sorted_first_names.txt Ranking files for Dennis in sorted order 3 years ago
sorted_last_names.txt Ranking files for Dennis in sorted order 3 years ago
sorted_word_frequency.txt Ranking files for Dennis in sorted order 3 years ago
style.css interface 3 years ago

README.md

LEGAL: If you are an undergraduate student at the University of Michigan, you are not authorized to access this website, should you choose to continue, remember you are bound by the honor code.

EECS398Engine

Think POSIXtive.

Search Engine Project for EECS 398 W19 at the University of Michigan

Folder Structure

bin All output executables, both for the app and for any tests and spikes.

buildAll object files. Removed on make clean

doc Any notes, configurations files, etc.

include All project header files. (*.h, *.hpp)

lib Any libraries that get compiled by the project or needed in development (don't think we'll have much use for this, but OpenSSL might have it.)

spike Small classes, test files, things currently in the early stages of development but you still want to have them committed to the repo on master branch.

src The program source files. No libraries *.cpp only.

test All test code files.

Makefile

Will start by just using a standard Makefile that works on Linux and Windows. If we need to do any real dirty platform specific stuff then we can use autotools but I don't see the need quite yet.

Style

The .astylerc file from Piazza is in the folder root. It should be run from the terminal before pushing to master.

TODO: automate style checking on git push.

Design Patterns

Should be an evolving thing but to start will be designing everything as self contained libraries. Header files in the include directory, Source in the src directory. Everything will compile easier with a Makefile.

TODO decide whether we want multiple executables (crawler, index, server, etc) or one executable that can do everything and is configurable from the command line.